3 ms·
It's funny when people mention Go as the gold standard of not adding features to the language and Rust as ever-changing when Rust hasn't introduced any major ch
by drogus 2y ago
It's funny when people mention Go as the gold standard of not adding features to the language and Rust as ever-changing when Rust hasn't introduced any major changes in at least 3-4 years and Go introduced a major paradigm shift in how people structure their code (generics).
Before you start replying with "Rust introduced X" - ask yourself - is X extending an existing feature slightly or does it introduce an entirely new concept?
- senorrib 2y agoGenerics is hardly a major paradigm shift, and these two languages are worlds apart in amount of features.
- drogus 2y agoThat's not the point, though. The author says: > Rust has arrived at the complexity of Haskell and C++, each year requiring more knowledge to keep up with the latest and greatest. Go was designed as the antidote to this kind of endlessly increasing language surface area. Yes, Rust learning curve is much steeper and the "language surface area" is big, but it's not changing much in recent years. Go getting generics is much bigger change than anything that Rust got in a long while.
- ilrwbwrkhv 2y agoYa the article is a bit fluffy and insubstantial. Surprising it's been voted up so highly on HN. Are people just going off the title?
- kunley 2y agoI think the author rather refers to "tamagotchi tooling" and constant adapting libraries to new trends. It was not that much about language changes per se
- drogus 2y agoI guess it depends on what libraries you're using, but honestly a lot of very popular libraries are at 1.x and hardly change. Honestly I'm not sure where people are getting these experiences from. I feel like either they make it up or they talk about experiences from 2017 or sth. Or maybe they are very unlucky when choosing dependencies?