Derby.js - a new look at web development

Are you a web developer?

For you, there is news.
')

What is the actual problem?

All web frameworks can be divided into groups. Each of these groups has its advantages and disadvantages.

Server oriented

For example: RoR , Django , Asp Net , Express.js
Generate html on the server.
This approach is good for static pages.
But as soon as you want to do something interactive, you start to drown in jQuery code.

Customer oriented

For example: Backbone.js , Knockout.js , Ember.js , Batman.js
Generate html directly on the client from templates. The code on the client is structured.
Good for interactive sites.
Does not eliminate the need to use a server-oriented framework, which leads to code duplication (models, validation, etc.)

Cross compiled

For example: GWT , Cappuccino
Allow to write everything in one language.
A very large level of abstraction.
Step to the right, step to the left - execution.

Also, none of the frameworks have mechanisms for synchronizing data between the client and the server and leaves the implementation of this to our conscience.

Let's dream

What do we want from a web framework?

• One language (Javascript) to reuse code on the server and client
• Generation of html for the first time on the server (for fast loading), the following times on the client (for interactivity)
• MVC for code structure
• Reactive view binding and model (model changes are immediately reflected in html and vice versa)
• Built-in data synchronization between the server and all clients
• Offline

This happens?

Yes, Derby.js

github
twitter
Questions are best asked in Google Groups
Sample application: habitrpg

Derby.js Creators: Nate and Brian

PS:
The main competitor is Meteor .
Of the benefits - below the threshold of entry. Of the minuses, it does not support npm and there is no html generation on the server.
A detailed comparison is here.

[ Derby.js materials ]