Angular.js vs Meteor.js vs Derby.js

After the post about derby.js and the translation of the comparison meteor.js and derby.js , the main question that was in the comments was something like: “What is still better than derby.js or meteor.js? And why all this is necessary when you can write on angular.js + express.js? ". Of course, it is not entirely correct to compare these frameworks, since derby.js and meteor.js are so-called full-stack, and angular.js is mvc on the client.

	angular.js (+ express.js)	meteor.js	derby.js
Full-stack framework	No, only MVC on the client.	Yes	Yes
Backend	Any	node.js	node.js
Console utility	Not	there is	there is
Dynamic link html with data on the client	Yes	Yes	Yes
Server html rendering	No, promise not native	Yes, not native	Yes, native
express.js app	Yes	Not	Yes
npm packages	can connect browserify	through the package own package manager o_O	browserify is built
Code Reuse Between Client and Server	Low	High	High
REST API	No, but easy to add.	There is a package	Yes, built
Database	Any	Any, but on the client, the Mongo Queries syntax	Any + necessarily Redis (for pub-sub and OT operations cache)
Synchronize data between clients	No, hard to add	Optimistic (who had time, he shot)	OT (like Google Waves)
Data Sync Channel	Not	DDP protocol (web-sockets)	browserchanel (as in Gmail, because web-sockets do not guarantee the messaging order)
Update application without rebooting (development convenience)	Not	Yes - html, css, js	Yes - html, css
Ready for production	Ready	Ready	Ready
Production examples	Thousands of them	Enough	lever.co , unroll.me
Current version	1.2.0	0.6.5.1	0.5.9
Entry threshold	Average	Low	Tall
Communi	Very big	Large	Small
If called in one word	Fashionable	Sweet	Excellent
Site	angularjs.org	meteor.com	derbyjs.com

')
If something is not correct / add / remove, write in comments.

Derby.js materials