bnolsen

5 ms·

1.
by bnolsen 20d ago
buz, a fork of bun right before the rust rewrite, claims sub second incremental builds just by using what zig itself provides. https://micrologics.org/blog/architecting-sub-second-javascr...
2.
by bnolsen 3mo ago
C++ and rust make these optionals ugly. Zig does it right. Zig also forbids null pointers and requires use of optionals.
3.
by bnolsen 3mo ago
That's called a fat pointer. Null terminated c strings is the majority of memory errors out there.
4.
by bnolsen 3mo ago
I was doing this for remote sensing orthorectification work back in 2004/2005. It works very well across multiple types of imaging sensors.
5.
by bnolsen 4mo ago
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.
6.
by bnolsen 4mo ago
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.
7.
by bnolsen 4mo ago
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.
8.
by bnolsen 4mo ago
Zig fails unit tests if there's a memory leak in those tests.
9.
by bnolsen 4mo ago
One of the core design principles of zig is no implied behavior.
10.
by bnolsen 4mo ago
Unit tests in zig will fail if the tested code leaks memory.
11.
by bnolsen 5mo ago
I guess the 'zit' name was already taken by something else.
12.
by bnolsen 5mo ago
The radeon 8500 deserves to be on that list. It still has active Linux support under mesa.
13.
by bnolsen 5mo ago
HTML is not something to hold up as the standard for documentation.
14.
by bnolsen 6mo ago
Why not just use zig for the entire thing?
15.
by bnolsen 7mo ago
Not to be confused with zlib.
16.
by bnolsen 7mo ago
Except for all the baggage it carries along with it including hacks to address baggage resulting in a very bloated language.
17.
by bnolsen 8mo ago
Quaternions are left handed spinors. Please use the correct unified math models (clidfford algebra) rather than these 3d only hacks.
18.
by bnolsen 8mo ago
Having worked with c++ strings and also string views I find zigs simple fat pointer to be fairly direct and straightforward, and a bit refreshing. Ownership is being coupled in with the type..
19.
by bnolsen 9mo ago
And then zig shows up...
20.
by bnolsen 9mo ago
It's christmas and not april fools!
21.
by bnolsen 9mo ago
I remember seeing this a long time ago and liking it, I just didn't have a use for it at the time. How does it stack up against luahit for perf and memory, and threading? It also looks like it could be worth looking at porting the com
22.
by bnolsen 9mo ago
Work gave me an m1 pro with 32gb on it. A year ago I put together one of those minisforum board+laptop apu with 64gb ram and 2tb nvme for not much money at the time, likely 500usd. For the performance sensitive software I was working on t
23.
by bnolsen 9mo ago
There's active work towards that (which could run as part of CI) and it looks very promising: https://github.com/ityonemo/clr
24.
by bnolsen 9mo ago
Zig actually does bring some new and innovative ideas to programming. While Zig itself may not become the next big thing a lot of ideas in it most certainly will find their way into languages moving forward.
25.
by bnolsen 9mo ago
And they tried to hang him for it. I wasn't particularly pleased with some actions he took after he ran off but the government reaction was truly out of hand and forced him into full survival mode. This part of government is full of w
26.
by bnolsen 9mo ago
they are very awkward to use in the current STL, they are part of the template definition. Back in the day EASTL did allocators much better but it never became a thing.
27.
by bnolsen 9mo ago
This confuses me. In zig null pointers are illegal, and I have yet to run into any case that should be addressed by using pointer arithmetic, that's all taken care of with slices.
28.
by bnolsen 9mo ago
you could fully redesign libc to be modern and toss out the null terminated string concept and use fat pointers and slices. But at that point why not consider moving onto a more modern language with things like explicit type conversions, m
29.
by bnolsen 9mo ago
I might buy your argument except that without corporate sponsorship for zig several projects using a very young and unfinished zig exhibit world class performance and utility, apparently without herculean effort.
30.
by bnolsen 9mo ago
'const expected: []const u32 = &.{ 123, 67, 89, 99 };' also works.

More ›