4 ms·
Hum... The Great (Web) Frontend Revamping seems to have passed. Nowadays people are still discussing if React or Vue is better, with a clear intonation of "what
by marcosdumay 4y ago
Hum... The Great (Web) Frontend Revamping seems to have passed. Nowadays people are still discussing if React or Vue is better, with a clear intonation of "whatever works for you, I prefer X".
Looks like the field is maturing.
Either that or we are on a fake calm before we see a lot of articles about people migrating into wasm in "whatever language has support for it right now" (AFAIK, currently wasm goes with rust).
- sircastor 4y agoThis doesn’t feel that different to me from ~2010 era jQuery vs Prototype vs …Dojo(?) these things happen in waves. I’ve wondered if the next revolution will be wasm, or another round of JS magic… or something different.
- darepublic 4y agoDon'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 agoThe 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 agoIt'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 agoThat'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 agoyou 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]
- jansan 4y agoIf you started with Vue two years ago, you had to learn Vue 3 shortly after that. With a new Vuex. Which has been dropped since in favor of Pinia. Oh, Vite has been developed since, so you may want to add this to your stack, because it makes compiling during development so much faster. Also, be aware of all the breaking changes that Webpack 5 has introduced. I hope front end development will be more stable in future, but the last two years where full of pretty major changes.
- suction 4y agoThe Vue 3 disaster (in my opinion) shook my trust in the framework forever. I immediately knew this is not a framework I will spend any more time in. What if I "upgrade" my apps to 3 and then Vue 4 comes along with yet another fundamentally different concept? This is not acceptable for apps with any kind of long time support requirement. Yes I know, Vue 2 paradigms are still usable in 3 but they feel very deprecated.
- KaoruAoiShiho 4y agoDon't think Vue 2 to Vue 3 is that bad, certainly nothing like AngularJS to Angular. You can still conservatively upgrade piecemeal elements of your stack and most of the code still just works.
- gherkinnn 4y agoComing from Vue 0.x and 1, Vue 2 felt wrong. It didn’t know what it wanted. Classes and hooks and decorators and options and only some obscure combination offered acceptable TS support. Having only read the docs, Vue redeemed itself with version 3. There’s the options API we know and love from v1 and the new and intuitive composition API. The docs make it easy to decide and not to mix them up. And no useEffect fuckery.
- runarberg 4y agoI inherited a vue2 codebase with a vuex store, and upgrading to vue3 and pinia one component at a time over a course of 3-4 months was quite easy. The upgrade path is really clear and they did a good job making everything compatible so that it could be made gradually over a relatively long time.