Re:Why we chose Vue.js over React
by danabramov on Sunday December 11, 2016 @01:42PM
(#13152402)
I wouldn’t say React is “hacked together”. Perhaps you are referring to the React ecosystem? Facebook doesn’t build single-page apps with React, so naturally it doesn’t provide solutions for routing and similar concerns, so there is more churn as people are figuring this out together.
[ Parent
| on HN ]
Re:Why we chose Vue.js over React
by keyanzhang on Sunday December 11, 2016 @06:20PM
(#13154094)
Isn't https://messenger.com a SPA?
Could you expand more on "Facebook doesn't build single-page apps in React"? I hadn't heard that before.
Re:Why we chose Vue.js over React
by lucasmullens on Sunday December 11, 2016 @04:35PM
(#13153432)
Like, facebook.com isn't one big single-page React app. They use it for specific pages/features.
Re:Why we chose Vue.js over React
by irrational on Sunday December 11, 2016 @03:05PM
(#13152867)
Wait, do people use React for non-SPA websites?
I use React all the time for individual components on server-rendered pages. It feels like a natural extension to formerly monolithic Rails/Node/etc apps.
That said, when an SPA is called for I'd far rather use Ember and get routing, state and a hundred other things for free, without needing to bolt together an entire front-end framework from parts each time.
Of course, hence the focus on server-side rendering. It is quite difficult to do properly though. Facebook itself is not a single page application.
Yep! I find myself using React.js for complex forms/wizards on non-SPA websites far more often than using it to build SPAs.