3 ms·
Very cool! Side comment: one problem with modern web apps is JavaScript bloat. And one pressure on libraries is to keep growing. These two things seem to be at
by eob 13y ago
Very cool!
Side comment: one problem with modern web apps is JavaScript bloat. And one pressure on libraries is to keep growing. These two things seem to be at odds. It would be nice if someone created some kind of { CSS, js, HTML } build system that allows components to be built and packages separately.
- skw 13y agoI'm not entirely sure what you mean? Things like bower and component already fulfil these roles.
- fantnn 13y agoI think he means being able to pick and choose exactly what part of libraries one would need; with something like jquery most sites are only using a fraction of jquery methods
- tmzt 13y agoWell, component.io (http://component.io http://component.io) is such a system. You have a choice of routers (page.js is a very express-like option that works well), and you can pick and choose what other components to build into your application. Components are self-contained packages of html/css/js based on CommonJS modules and compiled using node. I use grunt-component-build along with grunt-contrib-watch to rebuild the css/js files on each change. I've been using W3C standards (DOM) as much as possible to keep third-party dependencies at a minimum, with shimming where required for cross browser support. An effects library that doesn't require jQuery would be a good addition to that environment. (Nothing against jQuery, but I want to leave out a selector engine on platforms that don't need it and just use the support in the browser.)