 The #JavaScript ecosystem is number 1 when it comes to volatility and fragility. Try building a project made in 2014, and you’ll know what I mean: Gulp doesn’t work, libsass doesn’t compile, etc. Well, today, it was dethroned by #Android (or, should I say, #Gradle). I have spent *hours* to revive a project from 2018 to just bump the targetSdk version. 90% of the time was spent with Gradle not working, even when presented with the same JARs as years ago! 3 comments
 @kytta how do you feel about https://faultlore.com/blah/c-isnt-a-language/ ? (I'm probably not capable of an intelligent conversation about this because it's not my world, but I do think about it. This is a polite way of dissuading you from putting too much effort into a reply, should you be inclined. 😋)  Советую не использовать gradle wrapper, это вот прям зло в чистом виде. И вообще ничего кроме самих пакетов SDK не обновлять без необходимости. |
Gregory's Server
Having said that, #C is probably my favourite language/ecosystem combo. Yes, there is no simple `npm install`, and build systems can be cumbersome, but I love how a complete ecosystem bootstrapping is basically `brew install gcc make cmake autoconf`, compiling is fast, and subsequent builds even faster. And you can compile most code from 30 years ago without much hassle.