[NERD_ALERT]

React is an industry standard tool. If you want to have relevant frontend skills you should know React.

[mablopoule]

As a long-time Angular user I had the exact same feeling, and was glad when I finally could switch job to one with a React and Next.js stack.

Which is when I truly discovered the state of the React ecosystem, and noped the f*ck out of it. Design systems that recreates the <strong> tag but with a React component, the abomination that is CSS-in-JS and "typed CSS", mixed with some of absolutely brilliant libraries with well-thought out APIs, mixed with "best practice" du jour made by clueless frontend devs rehashing arguments in a truly blind-leading-the-blind fashion.

And I do like React, and might probably use it again, but it has the downside of being the defacto choice for new devs, which creates a huge spread in the ecosystem quality that other "second languages" ecosystems such as Rust or Elixir won't tend to have.

(I know that I'm mixing a framework with a language, my point also stand for the whole JS/node ecosystem, just doubly so when you focus on the React side of the NPM ecosystem.)

[pjmlp]

Relevant frontend skills is what the browser supports, that will stay the same regardless of ASP.NET, Spring, Rails, PHP, express....

[rafark]

I don’t like this suggestion. I mean, it’s a good, solid suggestion. But I don’t like everyone using the same thing. A market dominated by a single entity means less competition which means less innovation.

If we didn’t have competition we’d all still be using jquery.

[NERD_ALERT]

I agree, but also I think it’s fair to say many FE jobs today are basically React dev jobs. I was really excited about Elm, but it seems like that’s not gonna take off.

[bitL]

Tell that to authors of angular, svelte, nuxt etc. They are all obviously missing something.

[suddenclarity]

He's saying you should know it since it's industry standard, not that it's always best.