3 ms·
Alongside the work on server components, they also deprecated Create React App, which was previously the official way to create new apps for development, and wh
by rmccue 3y ago
Alongside the work on server components, they also deprecated Create React App, which was previously the official way to create new apps for development, and which had pretty good ergonomics. However, you won't find that documented on the actual CRA site - when you go looking for why your dependencies are out of date, you'll find references in obscure GitHub issues: https://github.com/reactjs/react.dev/pull/5487#issuecomment-1409720741 https://github.com/reactjs/react.dev/pull/5487#issuecomment-...
As much as I like the React team and appreciate their willingness to try things (and hooks have grown on me a little), they are human, and I think some of the decisions and direction they've taken things is a mistake.
I was part of the team who deliberated on the decision to use React over Vue in WordPress, and one of the reasons for my personal preference towards React was that it embraced JS rather than inventing a whole bunch of new things - yes, there was the funky syntax of JSX, but aside from that all the statements were regular JS, and it was much easier to conceptually understand than learning a new language. Hooks started taking us away from that, with weird functions that magically encapsulate state, and things like suspense and server components have strayed further from the light.
Making things like Next the official pathway to getting started with React is great and all for people building Node SPAs, but there's a whole wide world of software outside of that bubble, and I hope the React team peers out a little more often.
- andix 3y agoVite is the new unofficial CRA. Superior in nearly every aspect.
- ervine 3y agoMan I agree with all your comments so far. You get it!
- rmccue 3y agoThat may be the case, but the communication on the changes is terrible. I only noticed CRA was even deprecated after needing to dive deep into upgrading a dependency, and eventually stumbling over the GH issue comment. Like the original article, I’m just kind of annoyed at React about this. There’s probably great reasons to change (albeit, I don’t really think even that comment communicates them well), but it’s annoying.
- Rapzid 3y agoBut they pretty much snubbed Vite because it's not a "framework". Similar to how Tanstack Query doesn't even mention MobX as a state management library. It's crazy how many people use MobX for beefy apps(even Microsoft use it) but how little attention it gets.
- andix 3y agoMobX is awesome, but I never really liked HOCs. Recent React apps I made didn't have any global state management, there was no real need for it. I quickly evaluated zustand and liked the hook based API much better than mobX. Feels even more lightweight than mobX.
- Rapzid 3y agoI've mostly worked on apps(vs websites or however you want to make the distinction) so I keep appreciating being able to model the FE domain outside the view libraries with MobX. It works with Vue, React, Solid, and nothing. So it's there for me and allows for multi-view-library pages backed by the same stores.. Niche, but clutch for certain extensible apps.
- Rapzid 3y agoI'm not even sure what the deal is with suspense and the massive wait on it. They make it sound like it's some super advanced functionality you should never have to touch(because framework! so we'll not even tell you how to use it).. Yet Vue has had async component mounting forever and it just works. And it's so easy to understand they even explain it to you; you just return a promise that resolves to a component. Totally agree with your point about node backends. So much of the world doesn't and is not going to have their backend entirely or partially on node. But to the authors point, Vercel is Reacts daddy now and daddy needs to sell some hosting(for a new pair of shoes).