Ask HN: What would your dream web framework look like?
I am biased toward Django/Ember, so a lot of my ideas come from there. But I know some Rails as well as some Angular, Backbone, and Knockout.
My ideas:
0) Isomorphism via a CoffeeScript-like language that compiles to JS and Python, or a full-stack Node framework written in a CoffeeScript-like language.
1) Folders for server, client, and shared code. And maybe more folders to build a Replicant/Android client with something akin to NativeScript.
2) Support server-side rendering for faster loading in the browser (a la Ember FastBoot).
3) A Model which contains the definitive representation of real-world objects. DB interaction, validations, forms, serializers, etc. all derive as much as possible from the model. Model "classes" have field instances which, in one place, define how they fit in the database and what developers/end-users can do with them. Inspired by Django and, to a lesser extent, Ember.
4) Don't Don't Repeat Repeat Yourself Yourself. See 0, 1, and 3.
5) Real-time with no need for more than one or two lines of code to opt in and make it work. New, updated, or deleted models publish automatically, notifying something like a Django class-based view, which pushes the new data to all clients subscribed to that view.
6) Declarative templates like Ember. But even a basic operation, such as updating a template when an attribute in the model changes, has a default (replace part of the template to reflect the new data) which can be overridden easily to get animated updates, without jumping through hoops and/or accessing private APIs.
7) First-class support for indented languages such as Emblem, Sass, and CoffeeScript (or a similar language).
8) Free as in Freedom. Preferably AGPL, but LGPL or Apache--with its explicit patent grant--could work if a more permissive license is needed to promote adoption.
Your ideas?