Arto Bendiken artob

Rust maintainer perfectionism, or, the tragedy of Alacritty

I did not submit this to Hacker News and did not intend that this post would have high circulation but have no real problem with it being there or with it having such. I have more recent comments below. This post is from January 2020 and predates the Modular Font Editor K (MFEK) project.

I have not worked on Rust projects in quite a while, and don't know if I ever will again. I feel many crate maintainers are way too perfectionist, for example, despite all the developer hours that went into this PR, it took the effort within years to be (halfway) merged.

There's always a reason not to merge, isn't there? It would be better done with a new nightly language feature, or the function signature should have a where clause, or the documentation is not perfect. There's always a new nit to pick in the world of Ru

Let's Destroy C

I have a pet project I work on, every now and then. CNoEvil.

The concept is simple enough.

What if, for a moment, we forgot all the rules we know. That we ignore every good idea, and accept all the terrible ones. That nothing is off limits. Can we turn C into a new language? Can we do what Lisp and Forth let the over-eager programmer do, but in C?

proto3 Canonical Encoding Rules (CER)

This defines a set of encoding rules for Protocol Buffers 3 (proto3) for serializing messages deterministically such that the serialized form is suitable for signing and encoding in cryptographic attestations (ex. Merkle trees). Similar to ASN.1 and Cap'n Proto, a set of "canonical encoding rules" (CER) is used to define a canonical encoding where the basic proto3 specification does not do so. In this sense, the default protocol buffers specification provides a set of "basic encoding rules" which are not deterministic, and we extend that specification to support deterministic encoding for cryptographic use cases.

nvm vs Volta

A comparison of nvm and Volta to manage Node.js projects (without Yarn).

Bootstrapping a Project

Bootstrapping a Project with nvm

nvm install

example: https://medium.com/swlh/build-and-use-go-packages-as-c-libraries-889eb0c19838

https://medium.com/@walkert/fun-building-shared-libraries-in-go-639500a6a669

https://www.darkcoding.net/software/building-shared-libraries-in-go-part-2/

https://karthikkaranth.me/blog/calling-c-code-from-go/

	package main
	import "fmt"
	func main() {
	fmt.Println("hello world")
	}

	// c version:
	// #include <erl_nif.h>

	// static ERL_NIF_TERM hello(ErlNifEnv* env, int argc, const ERL_NIF_TERM argv[])
	// {
	// return enif_make_string(env, "Hello World!", ERL_NIF_LATIN1);
	// }

	// static ErlNifFunc nif_funcs[] = {"hello", 0, hello};

	# Creates a "dummy" network interface
	# we'll configure this interface with a link-local address
	# See: https://www.freedesktop.org/software/systemd/man/systemd.netdev.html
	##

	[NetDev]
	Name=dummy0
	Kind=dummy

	use std::str;

	fn main() {
	// -- FROM: vec of chars --
	let src1: Vec<char> = vec!['j','{','"','i','m','m','y','"','}'];
	// to String
	let string1: String = src1.iter().collect::<String>();
	// to str
	let str1: &str = &src1.iter().collect::<String>();
	// to vec of byte

	/* Ripped from https://www.tutorialspoint.com/sqlite/sqlite_c_cpp.htm */
	#include <stdio.h>
	#include <sqlite3.h>

	int main(int argc, char* argv[]) {
	sqlite3 *db;
	char *zErrMsg = 0;
	int rc;

	rc = sqlite3_open(":memory:", &db);