4 ms·

I'm all for shitting on the JS ecosystem, but honestly there haven't been any noticeable shifts whatsoever in its ecosystem for at least 6 or 7 years now. Both

by ratww 5y ago

I'm all for shitting on the JS ecosystem, but honestly there haven't been any noticeable shifts whatsoever in its ecosystem for at least 6 or 7 years now. Both React and Vue.js are now older than jQuery was when both were released. Same for Babel and Webpack. Typescript is older than all of these. SASS/SCSS also older than Typescript. Those are the only things you see in 99% of the frontend job descriptions out there. If anything, frontend is kinda boring, and it can be argued that some of those tools above need some disruption.

avereveard 5y ago
They keep releasing versions that break backward compatibility forcing whole app rewrite left and right, that counts too
- treeman79 5y ago
  Had a year long project in Angular. Most of the time was spent rewriting the app and learning the right way “again”
- ratww 5y ago
  The track record for compatibility in the tools I mentioned is extremely good. Even when new approaches were launched (Hooks, Composition in Vue), backwards compatibility was kept. You can even mix and match approaches in the same app. Of course there's Angular, but that's the exception to the rule. Heck, Microsoft has completely changed the way of writing native Windows apps in the last 10 years more ways than Javascript frameworks have introduced new stuff. Apple even changed the language to one that (unlike Typescript) is not backwards compatible. Complaining about the JS ecosystem evolving too fast is anachronistic, that happened more than 8 years ago.
  - CRConrad 5y ago
    > Heck, Microsoft has completely changed the way of writing native Windows apps in the last 10 years more ways than Javascript frameworks have introduced new stuff. No they haven't. You still write them in Delphi or Free Pascal / Lazarus just the same way you did ten years ago. Oh, you meant "the way of writing native Windows apps" with Microsoft tools? Yeah, well... Heard the old joke about the guy who complains, "Doctor, doctor, it hurts when I do this!"? My answer is the same as the doctor's: Well, don't do that then.

by ratww 5y ago

avereveard 5y ago

They keep releasing versions that break backward compatibility forcing whole app rewrite left and right, that counts too

treeman79 5y ago
Had a year long project in Angular. Most of the time was spent rewriting the app and learning the right way “again”
ratww 5y ago
The track record for compatibility in the tools I mentioned is extremely good. Even when new approaches were launched (Hooks, Composition in Vue), backwards compatibility was kept. You can even mix and match approaches in the same app. Of course there's Angular, but that's the exception to the rule. Heck, Microsoft has completely changed the way of writing native Windows apps in the last 10 years more ways than Javascript frameworks have introduced new stuff. Apple even changed the language to one that (unlike Typescript) is not backwards compatible. Complaining about the JS ecosystem evolving too fast is anachronistic, that happened more than 8 years ago.
- CRConrad 5y ago
  > Heck, Microsoft has completely changed the way of writing native Windows apps in the last 10 years more ways than Javascript frameworks have introduced new stuff. No they haven't. You still write them in Delphi or Free Pascal / Lazarus just the same way you did ten years ago. Oh, you meant "the way of writing native Windows apps" with Microsoft tools? Yeah, well... Heard the old joke about the guy who complains, "Doctor, doctor, it hurts when I do this!"? My answer is the same as the doctor's: Well, don't do that then.