Hacker News Reader

Comment by nromiun | Hacker News Reader

Is there any proposed timeline for a stable release? Big features like the recent async IO shows the language is very unstable right now.

View on HN

Andrew's take is "it's ready when it's ready but we hope it's good enough before it's fully ready that you want to use it anyway".

It's different and I like it. You get one shot at it and may just as well get it right in as many areas as possible.

Yep. He mentioned recently in his JetBrains interview he wants Zig to be a language for the next 50 years. Rushing 1.0 for the sake of signaling to the wider industry today would be actively harmful to that goal.

Yes. And this kind of mentality is a near extinct in modern software development.

Too bad it will not be adopted for anything serious in the next 50 years. There is no reasonable value proposition from a business standpoint for picking zig over rust. It is already the reality in much of the tech industry that Rust is filling the space previously occupied by C++. The fact that there now exists a safe low level language is legitimately a paradigm shift. It doesn't matter how many shiny cool things zig adds, being unsafe means it a technology stuck in the past.

There is no ETA on 1.0, but breakage has followed the pattern of it not really being hard to upgrade to a newer version, as it is very well documented on the version release notes.

writergate was not smooth, a lot of things that moved over to writer (Writer.Allocating for instance) had no documentation and I had to go read the zig source code to figure it out. the docs were just "instead of That use This"

nitpick: The language is pretty stable, what changes is the standard library.

Reply on news.ycombinator.com