3 ms·
Other languages debate for years, because they have a customer base with important applications into production that don't find funny that their code is broken
by pjmlp 9mo ago
Other languages debate for years, because they have a customer base with important applications into production that don't find funny that their code is broken with experiments.
Zig is years away to become industry relevant, if at all, of course they can experiment all they like.
- Pay08 9mo agoObviously, that comes with the language being in beta. If you don't want things broken, use a complete language.
- zarzavat 9mo agoIt's hard to imagine Zig ever becoming stable and conservative. Even at 10 years old, it's still as beta as ever. At some point the churn becomes part of the culture. Not a complaint, just an observation. I like that they are trying new things.
- Pay08 9mo agoI wouldn't be so sure about that. I do think there's a bit of scope creep, especially with the LLVM replacement stuff, but I don't think it's bad enough for the language to never come out. Most notable languages have at least one large corporate sponsor behind them, Zig doesn't.
- the_mitsuhiko 9mo agoI’m a casual user and the 0.16 changes scare me. I tried multiple attempts now, even with full LLM support to upgrade and the result is just a) painful and b) not very good. I have high doubts that the current IO system of 0.16 will make it for another release given the consequences of their choices.
- kristoff_it 9mo agoHere's some advice: 1. if you're a casual user (ie you don't follow the development) don't try incomplete APIs that not even the creators of fully know how they are supposed to work (because they're still tinkering with them) also you can't expect docs until the design is somewhat finalized (which is not yet, fyi) 2. llms don't help when trying to make sense of the above (a feature that is not complete, that has no docs other than some hints in commit messages, that changes every other commit), reserve llms for when things are stable and well documented, otherwise they will just confuse you further. If you want to try new features before they land in a tagged release, you must engage with the development process at the very least.
- jsheard 9mo ago> if you're a casual user (ie you don't follow the development) don't try incomplete APIs that not even the creators of fully know how they are supposed to work Is the completeness of each API formally documented anywhere? Maybe I missed something but it doesn't seem like it is, in which case the only way to know would be to follow what's happening behind the scenes.
- Zambyte 9mo agoZig cuts releases. This API is not on a release of Zig yet. It's only available through nightly builds of master. "Casual users" should stick to releases if they don't want to deal with incomplete APIs.
- the_mitsuhiko 9mo agoThat's not really the issue. The stable API is incompatible with the API that will launch with 0.16. It's not really relevant if I'm playing with incompletely API, I want to know how I can migrate to it. I did not move yet to 0.16, but I wanted to see. The migration pain will be the same once it launches unless they revert back, which does not seem likely at all. But the point is: potentially every API is unstable.
- 9mo ago
- deleted 9mo ago[deleted]
- nickorlow 9mo agoI think it benefits the overall ecosystem for them to experiment so other languages can take what works