4 ms·

Not sure how exactly React became so standard, but I'd assume it was a combination of the backing of Facebook and the frustration with performance and developer

Not sure how exactly React became so standard, but I'd assume it was a combination of the backing of Facebook and the frustration with performance and developer UX of Angular, which was most popular at that time. In our case, we had started a large project with Vue because most of our small team was familiar with it, but our tech lead decided to pivot to React because we had so much trouble hiring for Vue development in our city.

chipdart 2y ago
> Not sure how exactly React became so standard, but I'd assume it was a combination of the backing of Facebook and the frustration with performance and developer UX of Angular, which was most popular at that time. I believe React became so standard because it provides the right abstraction for managing GUIs expressed as a tree of compostable UI components and controls that are automatically updated when it's underlying view model is updated. It's approach is so well-suited to the problem domain. I frankly do not understand why Next.js managed to get any traction at all. I dare say that it was kind of forced upon the whole world with create-react-app dropping out of favour and newbies looking to quickly create barebones React projects.
- metaloha 2y ago
  "Compostable" is correct :D React is what happens when you misunderstand the purpose (and principle) of web components, then double-down and encourage framework-related libraries to sprout up around it. React is what gets used by companies who didn't do enough due diligence into deciding on the best tools for the job. I've worked with React and find it endlessly annoying and arbitrarily designed for the most part (in a modern development context - probably it didn't seem so randomly assembled back when it was still relatively new).
- c0brac0bra 2y ago
  Composable components and automatic updates were not new to React though. I guess maybe the way it did it was better than previous frameworks, using the shadow DOM and stuff

chipdart 2y ago

> Not sure how exactly React became so standard, but I'd assume it was a combination of the backing of Facebook and the frustration with performance and developer UX of Angular, which was most popular at that time. I believe React became so standard because it provides the right abstraction for managing GUIs expressed as a tree of compostable UI components and controls that are automatically updated when it's underlying view model is updated. It's approach is so well-suited to the problem domain. I frankly do not understand why Next.js managed to get any traction at all. I dare say that it was kind of forced upon the whole world with create-react-app dropping out of favour and newbies looking to quickly create barebones React projects.

metaloha 2y ago
"Compostable" is correct :D React is what happens when you misunderstand the purpose (and principle) of web components, then double-down and encourage framework-related libraries to sprout up around it. React is what gets used by companies who didn't do enough due diligence into deciding on the best tools for the job. I've worked with React and find it endlessly annoying and arbitrarily designed for the most part (in a modern development context - probably it didn't seem so randomly assembled back when it was still relatively new).
c0brac0bra 2y ago
Composable components and automatic updates were not new to React though. I guess maybe the way it did it was better than previous frameworks, using the shadow DOM and stuff