bnolsen

of course the asus rog z13.

C++ and rust make these optionals ugly. Zig does it right. Zig also forbids null pointers and requires use of optionals.

That's called a fat pointer. Null terminated c strings is the majority of memory errors out there.

I was doing this for remote sensing orthorectification work back in 2004/2005. It works very well across multiple types of imaging sensors.

I personally think something like the qok format is a better way to go. Make something that performs well and is dirt simple to implement.

It's pretty sad it used to not be so bad in the US. This is what happens when ethics and morals are removed from the culture.

I would think that you might have a better time going from go to zig. You would have to provide a pattern for implementing the interface model go uses.

Zig fails unit tests if there's a memory leak in those tests.

One of the core design principles of zig is no implied behavior.

Unit tests in zig will fail if the tested code leaks memory.

I guess the 'zit' name was already taken by something else.

The radeon 8500 deserves to be on that list. It still has active Linux support under mesa.

HTML is not something to hold up as the standard for documentation.

Why not just use zig for the entire thing?