[Retric]

That’s a little far, old doesn’t mean good. The bleeding edge often gets abandoned, but tech has generally been improving over time. IMO, the sweet spot starts when something was a fad ~5 years ago and is still reasonably popular.

[DaiPlusPlus]

> IMO, the sweet spot starts when something was a fad ~5 years ago and is still reasonably popular.

That would mean it's okay to use Angular today, but dev trends (and Google's support "policy") would advise against that.

[yen223]

A good reason to wait a few years is precisely so that we have a clearer picture of what strengths and deficiencies a piece of tech brings to the table, especially out in the real world.

We have a good picture of how Angular and React works in production now. We cannot say the same for something like Svelte.

[_0w8t]

React is far from being stable. It deprecated a lot older API, added entirely new concept of hooks.

If one wants stability, then PHP has a way better track record.

[scrollaway]

Nonsense. React is extremely stable. It indeed added hooks, deprecating exactly nothing in doing so. React deprecations are very few and far between.

[DaiPlusPlus]

> deprecating exactly nothing in doing so

De jure deprecation, correct - but reading between the lines in Facebook's own blog article that introduced Hooks ( https://reactjs.org/docs/hooks-intro.html ), which put a bit too much emphasis on "There are no plans to remove classes from React.", which to me means they're definitely going to be deprecating class-based controls in the future.

[notriddle]

I can see three possible universes here, all of which end on everyone assuming that classes are going to be removed from React.

> There are no plans to remove classes from React.

They're totally going to remove classes from React.

> We are going to remove classes from React.

They're obviously going to remove classes from React.

> No comment.

They're totally going to remove classes from React.