I really appreciate how Zig is playing the long game. I'm a bit worried about how relevant they will be in the future due to the fast pace we're moving at right now with AI and all of this stuff, but I'd love Zig to become the next fundamental language for decades to come, so I think their approach is the right one.
I'm very excited about the future of Zig! I really love the conservative and measured approach they are taking. Unlike many others these days, they appear to prioritise doing things right over simply going as fast as possible and trying to grab as much attention as possible.
My issue with Zig is that Andrew Kelly keeps rewriting and rewriting and changing the design non stop.
At this point the project is a decade old, with no signs of ever getting more stable in the next one.
I am not saying this is bad for the language itself, I can understand the goal of getting it "right".
But for a language aiming to be a C replacement/alternative it seems to fail to understand that C being a language that barely changed over our lives is one of the core reasons for its success.
That stability makes accepting its compromises and design shortfalls easier.
Curious what design changes you're referring to specifically. I've been using the language for a couple years now and the language itself has undergone pretty minor changes, perhaps the biggest one being the removal of `usingnamespace`, which I don't think was that big a deal. Or are you referring to changes in the stdlib?
If you are prepared to accept a lot of compromises in the name of stability then, as you say, C is right there! You have no reason to adopt Zig or anything else, C will outlive us all.
If you're trying to offer something different than C, for people who aren't willing to accept those tradeoffs, then you have to do something different.
Github Gitlab should work with stripe to let projects gate PRs in the main repository, both for being in queue & jumping the queue for prioritization, solve sponsoring OSS for good.
I really appreciate how Zig is playing the long game. I'm a bit worried about how relevant they will be in the future due to the fast pace we're moving at right now with AI and all of this stuff, but I'd love Zig to become the next fundamental language for decades to come, so I think their approach is the right one.
I'm very excited about the future of Zig! I really love the conservative and measured approach they are taking. Unlike many others these days, they appear to prioritise doing things right over simply going as fast as possible and trying to grab as much attention as possible.
Thoroughly enjoyed this interview. Zig is blessed with a project lead who is a real one, a person with principles. Respect.
My issue with Zig is that Andrew Kelly keeps rewriting and rewriting and changing the design non stop.
At this point the project is a decade old, with no signs of ever getting more stable in the next one.
I am not saying this is bad for the language itself, I can understand the goal of getting it "right".
But for a language aiming to be a C replacement/alternative it seems to fail to understand that C being a language that barely changed over our lives is one of the core reasons for its success.
That stability makes accepting its compromises and design shortfalls easier.
They need to take their time and break things now in order to become a language that barely changes later.
Curious what design changes you're referring to specifically. I've been using the language for a couple years now and the language itself has undergone pretty minor changes, perhaps the biggest one being the removal of `usingnamespace`, which I don't think was that big a deal. Or are you referring to changes in the stdlib?
What if you could rewrite your zig code with AI ?
If you are prepared to accept a lot of compromises in the name of stability then, as you say, C is right there! You have no reason to adopt Zig or anything else, C will outlive us all.
If you're trying to offer something different than C, for people who aren't willing to accept those tradeoffs, then you have to do something different.
Github Gitlab should work with stripe to let projects gate PRs in the main repository, both for being in queue & jumping the queue for prioritization, solve sponsoring OSS for good.