Zig Roadmap 2024 [video]

Very impressed by zig ambitions, but i found it very peculiar that their focus seems to be going &quot;down&quot; the stack ( aka, compiler infrastructure rewriting) rather than &quot;up&quot; (stdlib and lib ecosystem).<p>Am i wrong to feel a bit worried by this direction ? Is the team large enough do both at the same time ?

How about improving documentation? Last year I tried Zig and the documentation was abysmal. The majority of standard library functions had no documentation. The sparingly few examples that exist on the webpage didn&#x27;t work with the current Zig version and more. I say that as a Zig sponsor who wants to see research and innovation in the systems programming space. Documentation is maybe not as sexy as replacing LLVM with your own backend, but sorely needed.

TLDW: Andrew talk about the financials, the bug bounty program, the versioning strategy and the two main objectives on the short&#x2F;medium term: 1. Get rid of LLVM and 2. Improve compiler performance.<p>Then there is a Q&amp;A session.

Didn&#x27;t watch; will they implement RAII?

Comparatively<p>&gt; Incremental rebuilds cause a lot of compilation problems, bugs, and errors. Incremental rebuilds are also slow due to the amount of in between files generated between builds. Jai will contain no incremental rebuild steps. All will be compiled in one fresh compilation. This means that the compiler will need to run fast with high performance. The eventual goal is to compile a 1 million lines of code in 1 second, but as of right now, the compiler can only do 250,000 lines in 1 second.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;Jai-Community&#x2F;Jai-Community-Library&#x2F;wiki&#x2F;Philosophy-of-Jai#incremental-rebuilds">https:&#x2F;&#x2F;github.com&#x2F;Jai-Community&#x2F;Jai-Community-Library&#x2F;wiki&#x2F;...</a>