Post

👻 rossipedia 🎃
@rossipedia.com

Let's follow this journey. A user reads a blog post about getting started with React that mentions CRA. Let's see at what point they might get exposed to @vite.dev or the idea that CRA is a dead project! • npm: nope • github: nope • cra.dev: nope • react.dev: nope (at first glance)

10 reposts58 likes

👻 rossipedia 🎃
@rossipedia.com

Finally... after most likely scrolling down below the fold, they're presented with links to @vite.dev and Parcel However, NOT ONCE, has the user been presented with any messaging about the pitfalls of using CRA in the year of our lord 2025.

👻 rossipedia 🎃
@rossipedia.com

Vite is an absolute titan in the React community. I refuse to believe the React team is so obtuse that they can't see that this is a real problem, or arrogant enough to believe that they can, through sheer force of will, dictate that people learn react through a framework.

Thomas G. Lopes
@thomas.rocks

This and tanner's thoughts bsky.app/profile/tann... here put React in a weird position indeed. Guillermo recently posted on Xitter about how "React is like Linux" with React being the kernel, and the frameworks being the distros, and this all gets even weirder.

Tanner Linsley@tannerlinsley.com

"Framework" semantics get in the way of progress way too much with React and I'm really tired of the "you must be this tall" narative from react.dev. Tools that drastically aid you to be productive with React deserve a seat at the table. Vite is just the obvious start among many other tools.

Kamran Ayub
@kamranicus.com

This! It just adds more logs to the "React is a dumpster fire right now" argument. Plus, all the videos or even courses that aren't updated yet. We were told at Pluralsight to use CRA for all React courses because it (was) the simplest approach. Super frustrating for someone learning.