Realtime JS Frameworks
One thing I know we can all agree on is that realtime web apps are the future and the only way we will be developing web apps within a few years time.
Same or shared code and variables on server and client. For that, we need a same language. So, node.js is the only solution.
http://backstage.soundcloud.com/2012/06/building-the-next-soundcloud/ :: Building The Next SoundCloud - SoundCloud Backstage SoundCloud Backstage
http://stackoverflow.com/questions/3809539/choosing-a-web-application-framework-using-node-js/10357221#10357221 :: Choosing a web application framework (using Node.js) - Stack Overflow
https://workflowy.com/shared/c3000f25-d0fb-cf6b-6f72-bcb5d6a114ed/# :: Node.js Frameworks Comparison - WorkFlowy http://vschart.com/compare/tower-js/vs/flatiron/vs/socketstream/vs/derbyjs :: Tower.js vs. Flatiron vs. SocketStream vs. Derby – vsChart.com
Built by a couple Google search guys. http://techcrunch.com/2012/07/27/move-over-meteor-derby-is-the-other-high-speed-node-js-framework-in-town/ :: Move Over Meteor: Derby Is The Other High Speed Node.js Framework In Town | TechCrunch
https://github.com/codeparty/derby-ui-boot/ :: codeparty/derby-ui-boot · GitHub
Uses Racer for data sync Announcing Racer, experimental realtime model synchronization for Node.js - blog.nateps.com
https://groups.google.com/forum/?fromgroups#!topic/socketstream/RTMYDYniG0A :: Similarities to now.js - Google Groups
The most important difference is scalability. Nowjs does not have the plumbing necessary to persist sessions and pub/sub info to a common store so when a client gets disconnected they can reconnect to any process and pick up where they left off. You’d have to write that yourself with Nowjs. It’s a core concept in SocketStream.
Others: http://towerjs.org/ :: Tower.js - Full Stack Web Framework for Node.js and the Browser