4 ms·
I like what you've described but how different is that from just including jQuery to add some dynamicism to your page? Which, BTW, is what I think JS should rea
by 0x445442 8y ago
I like what you've described but how different is that from just including jQuery to add some dynamicism to your page? Which, BTW, is what I think JS should really be used for.
- martin_drapeau 8y agoIts no different. React/Vue are modern evolution of jQuery. They allow you to organize front-end code with strict conventions and best practices. You can achieve the same result with jQuery and Backbone for example. But you'll need to discipline yourself a lot and good luck hiring developers (they all want to work on React and Vue).
- blauditore 8y ago> React/Vue are modern evolution of jQuery. I disagree. They are whole frameworks taking a completely different approach than jQuery, which is basically just a helper library. jQuery is useful as a tool for operating within an externally organized application (or otherwise mostly static DOM tree). It simplifies low-level operations like DOM element manipulation. Frameworks like React or Vue take a top-down, more declarative approach on how the DOM is built and updated. It's in many regards more powerful and more productive, but comes at a certain cost (setup complexity, total page size, certain aspects of performance). So, which tool is best for your project really depends on the individual use case.
- martin_drapeau 8y agojQuery plugins are extremely powerful. Look at fullcalendar.io as great example. Web 2.0 was entirely built upon that. I hate to see people dismissing jQuery and its legacy as just a library. There is a huge community built around jQuery and thousands of plugins. It ain't new and shiny but you can build anything with it. In fact, today jQuery is used on 97% of websites* while React and Vue are around 0.2%. I imagine that will change over time. * Top 10M Alexa ranked: https://w3techs.com/technologies/overview/javascript_library/all https://w3techs.com/technologies/overview/javascript_library...
- 0x445442 8y agoYeah, the minute you start reaching back to the server for a significant update to the client data model in order to support a view transition I think the benefits of SPA are lost. Granted I've only deployed one SPA to prod and that was an Ember application but I'm not feeling the love based on that project.
- nepeckman 8y agoNot GP, but I think the websites would be largely similar to the end user (multiple pages with dynamic bits). However, I think there is a notable architectural difference. Modern JS frameworks are much more focused on providing reusable components with clear methods of interop and communication. I think the codebase of a "multiple small SPAs" would be easier to reason about and develop than a jQuery tangle. But in terms of functionality, its probably not much different than sites from 10 years ago (I don't think this is a bad thing).
- michaelbuckbee 8y agoIt's a spectrum and what's being advocated is using the right tool for the right job. Rendering the marketing pages of the site -> HTML+CSS Need to add the tiniest bit of interactivity -> jQuery Have a "module" of functionality that -> SPA
- pier25 8y agojQuery is the old paradigm of micro managing the DOM with ES5 code. The new paradigm is using data binding with the latest language features.