HN user

deagle50

654 karma
Posts0
Comments358
View on HN
No posts found.

If he's so relieved that Bun/Anthropic are off Zig, then why trash Jarred? He should say thank you and move on.

What this looks like to me is Jarred sinned by selling to Anthropic (as opposed to setting up a 501c3 or whatever Andrew deems righteous) and now must be discredited.

Claude Fable 5 1 month ago

you implied that not being given early access could bias you in the other direction. Which in my opinion would demonstrate that you are easily biased. Which would then call into question any opinion you share about the subject.

Why would I roll custom allocation strategies in Go (and then be accountable for supporting them) that affect multiple teams and services when I can have an LLM port to Rust and get dozens of additional benefits?

the compiler can now allocate the backing store for slices on the stack in more situations

Any details on when this happens?

Go is still not good 11 months ago

I mean, in 2025, not having crypto in stdlib when every man and his dog is using crypto ? Or http when every man and his dog are calling REST APIs ?

I'm not and I'm glad the core team doesn't have to maintain an http server and can spend time on the low level features I chose Rust for.

This is wild, thank you for sharing. An I agree with you, something this heavy in the year 19 seven zero was probably out of another universe.

I agree that it makes some things easier (at the expense of managing constructors/destructors), I'm disputing the blanket assertion that it's superior to manual management, in the context of Jai (and Odin). You're also introducing a reference count, but that's besides the point.

In Jai/Odin, every scope has default global and temp allocators, there's nothing stopping you from transferring ownership and/or passing pointers down the callstack. Then you either free in the last scope where the pointer lives or you pick a natural lifetime near the top of the callstack, defer clear temp there, and forget about it.