I just discovered http://formatjs.io/. It is a standard for i18n which exposes a couple of shared libraries that can be used by framework specific binding packages. They do this for react, ember, handlebars & dust for now. I wish I had known about this when I wrote my original post. Perfect implementation of what I was trying to communicate.

It’s definitely possible to create an ecosystem of packages that can be reused by multiple frameworks.

With ES6 and proper build tools it’s becoming easier to escape dependency hell as well. If one dependency is using lodash and you yourself are using lodash it’s possible that lodash will only be included once. Also, with ES6 having so much functionality as standard, the need for libraries like lodash is reducing.

There are many more aspects of web development that should have been solved once and for all already. Another example would be routing. The router is different for every single framework. React-router & Ember share the same philosophy yet none of the same code. Angular2’s router is supposedly very similar to Ember’s as well. Imo they should all be sharing code to deal with the generic stuff. The only difference should be how the configuration is passed from the framework to the core library.