Ask HN: Advantages of Browserify over Require.js for SPA development?
Hello Hacker News,<p>I have been working for quite some time with require.js on my frontend project, and enjoy a few points:
- the modular approach that allows lazy-loading parts of your application only when the user requests it
- taking advantage of the paths array to load from a CDN first, and fallback on a local resource if the former fails.
- its simplicity<p>However I particularly dislike the fact that development code and production code is different (as one goes through r.js), and I am not a particular fan of the syntax (common.js declarations looks actually simpler)<p>I have seen lately that people move over to Browserify, and some say it represents the future of frontend development: I was wondering what people who did the move thought were real advantages for Browserify over Require.js.<p>Disclaimer: let's remember the context: code that goes to production, not small testing projects.<p>Thanks for your inputs.
0 comments
—