React came out less than a year ago and there are already
alternatives built on the virtual DOM concept
How is it a bad thing?the virtual DOM should be a library by itself i believe. So should be angular injector , so is Sizzle ,etc...Instead of writing big frameworks that mashes up a lot of stuffs, these libraries should AND will be more modular no matter what, in the future. I want to be able to create my own library with building blocks ,like in any other language. The problem today is
1/ javascript lacks of a proper module spec
2/ libraries are too tightly coupled
ES6 module are the answer and will change things.fortunatly.
I dont want to use React,Angular or Vue or whatever. I want to use building blocks to create my own framework. JS lib maintainers will have to change the way they write libraries to make them extentable and pluggable.
I don't. I think it's a great thing, I thought my comment was pretty clear that I think "too many options" is B.S.
The OP is talking about a real problem. Unfortunately I don't see any good obvious solution, and I agree that everyone agreeing to use Framework X is not one.
React came out less than a year ago and there are already alternatives built on the virtual DOM concept, and attempts to port to other libraries.
X-Tag and then later Polymer came out which has acted as test beds for the Web Components standard.
Those are just two examples off the top of my head. Innovation is unlikely to happen if we all throw out hands up and agree to just use Framework X.