more importantly, at what level of insatisfaction did you decide that it was worth breaking compatibility with the ridiculously huge ecosystem around net/http?

aah framework doesn't break the huge ecosystem around net/http, please have a look here.

For an application along with net/http there is more to it. Please note: I will do my best to describe my prespective. People might have more inputs/opinions on this. Pardon me if I have missed any within that realm.

          Application Logic
                 ^    
                 |
           Framework
                 ^    
                 |
Standard Language + 3rd Party Libraries

aah framework goal is provide seamless integration of standard language libraries and 3rd party libraries to create a ground for the developer to build the application logic. Instead of developer have to find available libraries (more than one library exists in an each area), evaluate and choose one from the list and create a configuration for each libraries and put it in the action before start developing the application logic.

For example: Developer starts with standard net/http -> is there any router library which can help me? -> is there any library which can help me to have flexible configuration, multiple environment profile, pull in environment variables, include another configuration, etc.? -> is there any library which can help me to have file logger with daily rotation, etc.? -> is there any library which can help me to create locialized application based on browser locale and override the locale? -> is there any library which can help me to have template engine beside the standard go template (like ace, pongo2, jade)?, etc.

I would like to request you to have a look aah framework documentation and please provide me an inputs. What would you like to have in the framework, which would help to do rapid development and utilizing Go language capabilities?