3 ms·
This is why I'm surprised when production projects, like bun, choose to use zig. I don't think the language itself is a bad choice (although I do disagree qith
by thayne 1y ago
This is why I'm surprised when production projects, like bun, choose to use zig. I don't think the language itself is a bad choice (although I do disagree qith some of the design decisions), but having to make substantial changes when there are breaking changes like this because the language is pre-1.0 every so often in a large code base isn't something I would want to deal with.
- throwawaymaths 1y agomaybe... it's got some really good things going for it that are worth the pain.
- beders 1y agoZig just caught up with the practice that runs rampant in JavaScript land ;)
- toastercat 1y agothis comparison doesn't really make sense since JS as a language keeps a lot of old baggage to maintain backwards compatibility.
- flohofwoe 1y agoIn reality it makes little difference whether source code needs to be fixed because of a breaking language or dependency update. Even in C/C++ I need to go over my code whenever I update to a new compiler version because of new warnings.
- pjmlp 1y agoAnd that is why when no one pays the budget for doing tooling upgrades in big corps, the tooling never gets updated.