The Watercooler Squad is an important place for all things unimportant and nonsense at daily.dev. It’s designed to waste your time and distract you, buckle up 😻 🤹🏽‍♀️

Watercooler

The post covers a variety of topics related to dotnet, dotnet core, C#, and web development. It provides recommendations and information on current tech news.

React is still the most used framework for web dev, by a longshot. It inspired countless spinoffs, and is still a very important piece of software that billions of people interact with daily. It’s battle tested, has an incredible community, a thriving package ecosystem, first class support when it comes to any integration and is still used and recommended for any large (or small) project.
The fact that highschool kids are passionate enough to try new things and propose better alternatives does not make their source of inspiration “bad” or “the worst”.
It has it’s flaws, it’s ups and downs so to speak, but carpet statements about it being the worst does not paint the picture. Poking fun at the specific issues that react has would make for a better “inside joke” that would be more #relatable for those who have experience using it day to day. but hey i’m not the joke police, i’m just a snarky internet commenter

Luckily, React is not a framework, but a library 😜

fr, a highschool kid literally made a react clone way better, that’s how bad it is😭

I’ll concede that React is not the best toolset in terms of elegance or performance, but it gets a lot of value from critical mass adoption: There are many React solutions, and there are many people producing React content and new solutions. At implementation level, that means there’s less time to locate answers and existing packages/tools, which generally translates to faster time to market or fast speed to ship features.
Angular has a healthy adoption in more Enterprise-sy/.NET circles for similar reasons. It’s not elegant at all, and doesn’t try to be, but it’s another field where solutions and information is readily available and also easy to integrate.
For React, another thing working in its favor is that it has a relatively low spin up time: There’s no unique DSL that you have to grok, and JSX/components just look like a splattering of HTML and JavaScript, so a new frontend developer, or a backend developer that is transitioning to fullstack can easily start contributing fast.

yeah, react is definitely the worst web framework, because it’s not a framework. React is a Library.