4 ms·

> Frontend is a mishmash of random components and packages You could say the same about developing in Clojure, or Rust or Golang, but somehow you typically onl

> Frontend is a mishmash of random components and packages You could say the same about developing in Clojure, or Rust or Golang, but somehow you typically only see this same tired rhetoric applied to JavaScript.

lenkite 2y ago
No, you cannot say the same about Clojure and Golang. Those are extremely stable languages. Go lang esp has a batteries operated standard library that can be used to develop apps with excellent backward compatibility - you can get back years later, upgrade the runtime and build and deploy your project - and it will work without issues. The comfort you get is soothing. The same is certainly NOT true of JS where stuff breaks from month to month, build paradigms change yearly - causing severe amounts of deep stress. The rhetoric applied to JS is fully valid and justified.
- squidsoup 2y ago
  The philosophy of building apps with discrete libraries that do one thing well absolutely applies to js, clojure and golang. I have no idea what you’re referring to when you say things break month to month, that has not been my experience with js. Regarding paradigms changing yearly, also not true - have been building jsx apps for a decade and the only significant change has been from class based components to hooks, which was an easy and welcome transition. Things also change in all language ecosystems. Does anyone use lein these days? Not really.
  - lenkite 2y ago
    > I have no idea what you’re referring to when you say things break month to month, that has not been my experience with js. This is utterly jaw-dropping. There is simply no way to respond to this, since the Everest mountain representing the JS reality directly contradicts this. Its like saying one does not experience Newton's laws of motion. I think you should definitely hold a poll with the community. You would be the super, ultra minority who would hold this position. The only you would have avoided breaking stuff is if you stuck to plain old JS, avoided use of all frameworks, maintained all libraries yourself and did not use any build infrastructure. There is utterly no other possible way you have gone a decade without stuff breaking. React has changed so much - its tooling, libs, best-practices and idioms in the last decade alone. Comparing the JS versus Go ecosystem is like comparing a mad-max kraken with ten-thousand tentacles surfing the waves and wild on steroids vs a boring container freight-ship placidly making its way across the ocean. But yes, it can be fun to surf on the kraken.

lenkite 2y ago

No, you cannot say the same about Clojure and Golang. Those are extremely stable languages. Go lang esp has a batteries operated standard library that can be used to develop apps with excellent backward compatibility - you can get back years later, upgrade the runtime and build and deploy your project - and it will work without issues. The comfort you get is soothing. The same is certainly NOT true of JS where stuff breaks from month to month, build paradigms change yearly - causing severe amounts of deep stress. The rhetoric applied to JS is fully valid and justified.

squidsoup 2y ago
The philosophy of building apps with discrete libraries that do one thing well absolutely applies to js, clojure and golang. I have no idea what you’re referring to when you say things break month to month, that has not been my experience with js. Regarding paradigms changing yearly, also not true - have been building jsx apps for a decade and the only significant change has been from class based components to hooks, which was an easy and welcome transition. Things also change in all language ecosystems. Does anyone use lein these days? Not really.
- lenkite 2y ago
  > I have no idea what you’re referring to when you say things break month to month, that has not been my experience with js. This is utterly jaw-dropping. There is simply no way to respond to this, since the Everest mountain representing the JS reality directly contradicts this. Its like saying one does not experience Newton's laws of motion. I think you should definitely hold a poll with the community. You would be the super, ultra minority who would hold this position. The only you would have avoided breaking stuff is if you stuck to plain old JS, avoided use of all frameworks, maintained all libraries yourself and did not use any build infrastructure. There is utterly no other possible way you have gone a decade without stuff breaking. React has changed so much - its tooling, libs, best-practices and idioms in the last decade alone. Comparing the JS versus Go ecosystem is like comparing a mad-max kraken with ten-thousand tentacles surfing the waves and wild on steroids vs a boring container freight-ship placidly making its way across the ocean. But yes, it can be fun to surf on the kraken.