[Insensitivity]

I was looking at the Meet repository as an example, people literally don't know how to write React, without drowning in `useEffect`, `eslint-disable`, `any`. React has it's issues (and a ton of them), but writing code like this, I expect it to end up exactly like Microsoft Teams quality wise.

Honestly, at that point, it's indistinguishable from LLM slop

[moffkalast]

Why would one decide to even go with React in recent years anyway? Strangely I've seen it happen a lot too.

I'd have thought that Vue or Svelte would be a slam dunk choice. Do project managers love bloat and lag or something?

[Insensitivity]

I personally don't mind React, but I do acknowledge, after using it for a couple of years, that it seems to be a magnet for issues. It's the kind of framework, where if you're not writing properly, mostly like [Thinking in React](https://react.dev/learn/thinking-in-react) (with some caveat for niche performance optimizations), you're going to have a rough time, and you're going to make life miserable for anyone that does know what they're doing

It has a weird learning curve, where you can ship something somewhat working, fairly fast, but to write it properly, with no bugs, you need to understand a lot of niche React-specific things, and their solutions (and those solutions are never useEffect https://react.dev/learn/you-might-not-need-an-effect).

At that point, I wouldn't recommend it to anyone who isn't already experienced with React. It's been an uphill battle, trying to work with anyone that is using React, without understanding how to write properly.

[vldx]

The reactivity model fits well in real-time applications; perhaps SolidJS is better alternative in this context, though.

[shepherdjerred]

I have met very few devs who know how to avoid useEffect