Actually, I take it back. Don't turn Mojito into DerbyJS.
Leave the database stuffs out of the framework.
I want Mojito code to run transparently between the browser and nodejs, and rely on REST for querying/persisting data. I even blogged a bit about this too. :) http://www.phamcom.com/2012/07/ultimate-javascript-framework.html
Thanks.
QUOTE
(Ren @ 19 Jun 2012 12:27 PM)Very interesting, thanks!
I like the Racer component which handles data sync in the models.
I haven't looked in depth yet, but it appears their model stuff is more development than ours.
OTOH I believe we're going further with views and client/server interactions -- e.g. calling a server controller from the client, binders, etc.
Let us know what you think!