4 ms·
Seems more like they threw their hands up in frustration and went with something that was more immediately understandable to them. I haven't used Vue yet, but
by jmcgough 9y ago
Seems more like they threw their hands up in frustration and went with something that was more immediately understandable to them.
I haven't used Vue yet, but I'm curious how nice it is to develop with after the codebase has grown significantly - I remember Angular 1.x had that same "magic" that made it easy to appreciate and pick up, but ended up being a huge headache after writing production code with it for over a year.
And really, there's a reason why React isn't designed to work well with jQuery. That's one of its biggest strengths - writing code declaratively and letting it figure out what the correct state/DOM should be. I can't imagine trying to write a complex SPA and modifying the DOM directly - that was the reason Facebook came up with React to begin with.
- ng12 9y agoReact is the only web framework I've ever used that has held up to the trials of a long-lived application. I thought it was pretty good when I first picked it up, two years later and I'm in love with it. That alone makes me incredibly hesitant to try new frameworks.
- acemarke 9y agoOne of the nice things about React's component model is that it's fairly straightforward to wrap up imperative DOM manipulation like a jQuery plugin into a declarative React component (assuming the DOM manip is scoped and not page-wide). The React docs recently added a section on integrating with non-React code [0], and I've got links to several more articles discussing integration and interop at [1]. [0] https://facebook.github.io/react/docs/integrating-with-other-libraries.html https://facebook.github.io/react/docs/integrating-with-other... [1] https://github.com/markerikson/react-redux-links/blob/master/react-component-patterns.md#wrapping-non-react-code https://github.com/markerikson/react-redux-links/blob/master...