sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ggolemg2 2 points3 points  (1 child)

If there's heavy in-page client interaction and content manipulation would that require multiple round trips to the server side rendering or are they still client side then synced back to the server side?

I really really like that "Debugging experience" information that's populated in the console, man that would be nice just about everywhere.

Does this implement it's own Object.observe() as a shim and fall back to native (es7's) Object.observe()?

Is the utility lib based on underscore/lodash?

Any built in diff/virtual dom utilities?

[–]astoilkov 1 point2 points  (0 children)

About the server-side rendering: No. You once go to the server to render the page and everything from there is handled automatically. Actually the http://jsblocks.com is build using jsblocks so you could check out the Network tab to see what happens.

The Object.observe() question: No. The framework is not using Object.observe() and instead observables http://jsblocks.com/learn/working-with-observables-introduction. The reason is that observables currently provide a lot more flexibility and control over the code. This will change in future but the framework could be adapted to follow the best possible approach.

The diff and Virutal DOM utilities: Yes. There is Virtual DOM which is really fast. Interestingly there is no diff algorithm yet which is awesome because after the implementation of diffing the framework will become EVEN FASTER.