Comments URL: https://news.ycombinator.com/item?id=49334648

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49288683

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49247023

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49231430

Points: 20

# Comments: 0

For anybody reading, the project tracks new Zig to get all the new async I/O goodies but was hit by some regressions in Zig's translate-c because it recently became fully independent from LLVM.

Other contributors and I took this as an opportunity to contribute some fixes to translate-c and in my case I also switched for a bit to my other projects, mainly https://zine-ssg.io, which I had neglected for a few months while going all-in on awebo.

I plan to resume development of awebo in a month or two, I just want to leave Zine in a good spot before switching again (I have a bad time paging between different projects too often and prefer doing continuous work for a while before switching back).

And, unrelated to Bun, I too would disagree. You don't want to have to wait minutes for a build to complete before you can run the test suite, or even just know if there was a semantic error in your code. Build times are 100% a bottle neck for big-enough projects.

To be fair, there are caveats still in place today: Zig incremental compilation does not yet support aarch64 and only the linux linker supports binary patching, but it's just a matter of time before all major platforms are conquered.

Comments URL: https://news.ycombinator.com/item?id=49033099

Points: 305

# Comments: 191

Note that usage and public interest are not the same quantity, people also care about the potential of a project.

Comments URL: https://news.ycombinator.com/item?id=48843352

Points: 817

# Comments: 707

Comments URL: https://news.ycombinator.com/item?id=48539020

Points: 5

# Comments: 0

If you learn how to use arena allocators and in general use modern techniques, you don't need global reasoning to write correct memory management code pretty much never.

If your code is a RAII and abstraction maze, then yes, you will probably need global reasoning, but that's not the case with Zig.

I posted this link at the same time when I posted it to Lobsters (https://lobste.rs/s/g6lkw1/my_software_north_star) 3 days ago, but it didn't get on the front page. Seeing that the submission time has been reset, I imagine it was given a second chance by HN curators (it's a known process), but that doesn't mean free upvotes, it's just that some people resonate with the thinking.

In some ways it always has been, the community was 'born' in the middle of the pandemic, then for a long time there was a constant influx of Rust zealots coming into threads about Zig to remark how immoral it is to use Zig, and now LLM shovel sellers are telling everybody that the only way forward is to become efficient at consuming tokens.

But it's actually not that bad.

The Zig community is growing pretty well, useful software is being written in Zig, and the advantages that Zig brings are still valid whether you hand-code or use LLMs (e.g. cross-compilation of C/C++ code).

If Rust helps you get all the way to correctness, then great, but that blog post was insane.