HTTP/2, smaller is better
The new protocol is the bees knees. The browser vendors obviously think so, they’ve all gone and implemented it. Grid layout is obviously too much to ask for. Some of the new features in HTTP/2 like multi tenancy and header compression are really nice, even considering the tradeoffs they might have. For me the idea of loading smaller modules instead of larger bundles because it is faster is great news. Loading only those modules you need is faster again. The performance gain alone makes the modular approach the way all large sites will be built and http/2 they way they’re delivered.
ECMAScript 2015 (aka ES6)
Loads and loads of new features that have been a long time coming and modules being one of my favourites. A shame objects didn’t get much love but more is coming. Also fetch and async would be improvements over
XMLHttpRequest when dealing dynamic code and content. Especially with the rising popularity of API architectures.
A trait of modular web development is that a module wants to contain the markup, styling, UI behaviour, business logic, tests and documentation. A good module should be easy to build, easy to change and easy to throw away. This, to me, doesn’t sound anything like the traditional three silo approach of the web stack which is really easy to build, parts are usually somewhat changeable but most of the site is near impossible to remove. Legacy code is a major bugbear for any site above a certain size and a modular approach makes this less painful. Not pain free, but the opportunity for incremental change is a reality.