Why everyone who is building a new framework automatically assumes that speed is all that matter? You can compare speed of another framework, only when you have at least bigger part of the functionality that other framework offers.
It's pretty much the same as to compare drag race car with a luxurious BMW limo, yeah it might be faster and ok if that is all that you need, but in most cases you will pick medium speed but with all the features that comes in BWM...
You are correct. I believe performance is a must but not what is most important. You could see other interesting features like debugging experience in the framework. Server-side rendering I believe is also a really powerful feature.
http://jsblocks.com/learn/introduction-why-jsblocks#debugging-experience
Additionally, I have been developing jsblocks for the past two years and I think that it has a lot of features to build complete applications. However, you could give an example of what jsblocks does not have that other framework has. :)
For starters, right now I can only see a few true frameworks out there - Angular and probably Ember, the rest, like backbone, react and many other so called "frameworks" are only libraries. JSBlocks as I see it from documentation is also only a library, far from true framework.
Now the problem with libraries is that they offer too much freedom and with all that freedom comes loads of different approaches that are difficult to follow or even impossible at later stages... If you are willing to build your own framework out of library that might be fine, but if you want to work in a team and try to recruit members that already know a framework that might get tough and it will be even more difficult when problems stars rising with your "framework" and no answers could be found on stackoverflow or other resources...
Anyways, I believe that someone can compare full frameworks like angular only with another full framework otherwise it might be really unfair comparisement.
Agreed, speed matters if it as you said comes with a more efficient implementation that is far more developer friendly. With ES6 and soon ES7, notably Object.observe, we may be getting the best of both worlds. However, in terms of speed for jsblocks I do not see the server-side rendering feature as a plus or really even a feature.
Yes. ES6/ES7 are great but they are not ready yet. I am looking into ways to make jsblocks more ES6/7 friendly. Regarding the server-side rendering I believe it is very powerful feature. We use client-side framework to improve user experience and server-side rendering does improve user experience because there is no flickering before the framework kicks in. And if you cache the pages you will also get extra performance boost.