this got to hacker news somehow and now they are roasting me saying its not new or interesting. I have been programming for 26 years and have never encountered this pattern. I must be retarded https://news.ycombinator.com/item?id=44467607#44501697
nostr:note19ekkvgk3xe7z3cklj5s2cz0cr5yglr0qtsttfrkyt5vdz883tfaskvjxx4
Hello you!
You are proof that retarded people can be great innovators
hacker news is considerably less interesting than oot_bitset.
Screw they / them
It's not 100% rust and doesn't require buying a new SSD to store the cargo deps on, of course they ain't interested.
hacker news has become a circle jerk of people that only love one thing: AI.
anything else is "garbage" and "everyone knows it"
No one catches every pattern. Fuck em. You rock
Yes I knew about this pattern in high school but who cares
For those of us at the old school, dynamic allocation is something expensive and optional! Data structures like this come naturally.
In more complex systems, you have to assume dynamic allocation and deallocation everywhere. And so you rarely encounter code that is this straightforward: these patterns are lost.
Reminds me of the original ls source code: I have it on my laptop somewhere. It doesn't really use generic dynamic allocation. It uses brk to get room at the end of the program for its scratch buffer.
A different world.
even in Rust they are just starting to get the concept of custom allocators, strings allocate on the heap by default. why can't I use per-frame arena allocators for strings in my immediate mode ui!? its all getting tossed at the end of the frame anyways.
at least zig has made custom allocators more of a first class thing... but this is why I keep coming back to C.
haters gon hate
