3 ms·

"Ok you directly addressed one of my hand picked examples, clearly showing your point and why my example wasn't a good one. Now address all my other ones before

"Ok you directly addressed one of my hand picked examples, clearly showing your point and why my example wasn't a good one. Now address all my other ones before I consider your perspective might be valid!" This is like the comment version of the gish gallop.

whstl 1y ago
No, that's an answer to a cherry-picked reply. It was one package that had a version migration. I don't necessarily agree but I'm trying to move the discussion forward rather than staying at the "it's all shit" lane. And I gave three other examples, and I can give others: React itself has been around for 12 years, leading. Vue has been super stable too. Migrating versions of frameworks is several magnitudes harder than migrating the ESLint config, and ESLint is optional. Migrating versions of previous tooling like Babel or Webpack is several orders of magnitude more complicated than ESLint.
- collingreen 1y ago
  I'm not even against you in general but "react for 12 years" is another really bad example with the complete paradigm change from classes to hooks. I even think hooks are better, but I'm not going to sit and tell people their fatigue isn't valid when even your argument is "some of these aren't as bad as babel or webpack".
  - whstl 1y ago
    The paradigm change you mention happened once, it was piggybacked on an existing and very popular concept (functional components), and the previous paradigm was "deprecated" by the community itself. Sure it would be better if people had gotten it right the first time, but the fatigue problem isn't really due to React. And my argument isn't that "X is better than Y". It's that the number of new tools showing up is WAY smaller than it was when those complaints started. Today it has become a meme here in HN, often by people outside the frontend community.

3 ms·

"Ok you directly addressed one of my hand picked examples, clearly showing your point and why my example wasn't a good one. Now address all my other ones before

by collingreen 1y ago

whstl 1y ago
No, that's an answer to a cherry-picked reply. It was one package that had a version migration. I don't necessarily agree but I'm trying to move the discussion forward rather than staying at the "it's all shit" lane. And I gave three other examples, and I can give others: React itself has been around for 12 years, leading. Vue has been super stable too. Migrating versions of frameworks is several magnitudes harder than migrating the ESLint config, and ESLint is optional. Migrating versions of previous tooling like Babel or Webpack is several orders of magnitude more complicated than ESLint.
- collingreen 1y ago
  I'm not even against you in general but "react for 12 years" is another really bad example with the complete paradigm change from classes to hooks. I even think hooks are better, but I'm not going to sit and tell people their fatigue isn't valid when even your argument is "some of these aren't as bad as babel or webpack".
  - whstl 1y ago
    The paradigm change you mention happened once, it was piggybacked on an existing and very popular concept (functional components), and the previous paradigm was "deprecated" by the community itself. Sure it would be better if people had gotten it right the first time, but the fatigue problem isn't really due to React. And my argument isn't that "X is better than Y". It's that the number of new tools showing up is WAY smaller than it was when those complaints started. Today it has become a meme here in HN, often by people outside the frontend community.