4 ms·

Don't worry, view layer may be stabilizing but what about Managing backend requests is too complicated!(react-query) You need gql don't you? Don't forget f

Don't worry, view layer may be stabilizing but what about Managing backend requests is too complicated!(react-query) You *need* gql don't you? Don't forget forms. Super hard to do right. react-final form, react form hook, etc We need a monorepo framework! Nx, turbo, rush, pnpm (too low level), Lerna (too old and unmaintained) What about bundlers huh? Vite, esbuild, rollup, webpack I still see plenty of opportunity for teams to ignore persistent issues and just diagnose a new framework without analyzing their current woes. Silver bullets for everyone!

nicoburns 4y ago
The difference is that's all ignorable. If you want to standard React with classes, redux, npm and webpack like it's 2017 then you absolutely can, and it's still a maintained and supported solution. That's very different to say the evolution from JQuery to Backbone to AngularJS to React where you ended up being on an increasingly unsupported platform if you didn't upgrade.
- darepublic 4y ago
  It's not really ignorable, these frameworks come ready made with converts seeking to spread the good news to every codebase they find. Understanding, let alone improving, legacy code is a total waste of their awesome powers. It's raze the city and build paradise from scratch. Using shiny new framework (tm).
  - nicoburns 4y ago
    That's what tech leads are for. To be the person with experience and judgement who has the authority to set the rules for the rest of the team on these kind of questions. If you're having problems with this I'd suggest you have more of a hiring problem than a framework problem.
    - darepublic 4y ago
      you might be right on the money with that. I mean it also reflects badly on me in regards sort of jobs I find myself in where this is a recurring problem. But.. I feel like it may be more widespread problem than most people admit.
deleted 4y ago
[deleted]

Don't worry, view layer may be stabilizing but what about Managing backend requests is too complicated!(react-query) You *need* gql don't you? Don't forget f

nicoburns 4y ago

The difference is that's all ignorable. If you want to standard React with classes, redux, npm and webpack like it's 2017 then you absolutely can, and it's still a maintained and supported solution. That's very different to say the evolution from JQuery to Backbone to AngularJS to React where you ended up being on an increasingly unsupported platform if you didn't upgrade.

darepublic 4y ago
It's not really ignorable, these frameworks come ready made with converts seeking to spread the good news to every codebase they find. Understanding, let alone improving, legacy code is a total waste of their awesome powers. It's raze the city and build paradise from scratch. Using shiny new framework (tm).
- nicoburns 4y ago
  That's what tech leads are for. To be the person with experience and judgement who has the authority to set the rules for the rest of the team on these kind of questions. If you're having problems with this I'd suggest you have more of a hiring problem than a framework problem.
  - darepublic 4y ago
    you might be right on the money with that. I mean it also reflects badly on me in regards sort of jobs I find myself in where this is a recurring problem. But.. I feel like it may be more widespread problem than most people admit.

deleted 4y ago

[deleted]