It's great to have a liberally licensed alternative to Meteor and Firebase. Many thanks for that.<p>What I have taken from the article:<p>1. Derby is done by competent people
2. They support server and client code sharing
3. MIT license
4. NPM instead of proprietary packaging<p>I especially like 2). It was one of the killer features of Appjet which had code sections like: /* appjet:server <i>/, /</i> appjet:client <i>/, /</i> appjet:both */ You can guess what "both" did. Appjet was miles ahead for its time. I am sure David will take care of that part at Meteor's.<p>Last but not least, I don't like the name Derby. It is already used by a popular Java SQL database.
Looks like a lenghty review.<p>Why do all node.js based frameworks prefer nosql? And where are the discussion about automated testing and continuous integration/deployment?<p>I'd like to see a framework that support traditional RDBMS and makes testing in both server and clinet side easier.<p>Rails has set the bar higher...
Can we please start talking seriously about security around these frameworks. Exposing your DB API directly to the client is opening yourself to the equivalent of "rm -rf /" or "DELETE * FROM table".
I'd be curious to hear any takes on how other similar JS frameworks focused on "live" data binding (particularly Ember, also Knockout) stack up to these two newer players. Clearly Derby and Meteor strive to be more complete end-to-end solutions, but it's my understanding that this (generally speaking, and more long-term) is specifically a goal of Ember as well.<p>Also, the concurrency models of all the JS frameworks of this nature appear to be pretty immature at first glance. Derby is starting to attach parts of ShareJS, but I don't see much else that looks particularly promising in other frameworks. I'm not sure that you can "partially" implement OT (or mix-and-match parts of different solutions), which perplexes me about some of the code I've seen in the area, even in ShareJS.
I just tried the TODO app from the Derby home page and it is just doing xhr polling. I tested on Chrome and Safari.<p>The Metor and Firebase demos used both websockets.
Trying derby.js out now. Just so that you know you can write in Javascript and/or Coffeescript but the internal code and the examples are written in Coffeescript.