You appear to be advocating a new JavaScript framework.

(a checklist)

Your framework will not work. Here’s why it will not work.

You appear to believe that:

[ ] Existing frameworks have too many opinions that aren’t your own

[ ] Legacy browsers aren’t important

[ ] Convention is a bad thing

[ ] Your framework is the closest to “vanilla” JavaScript

[ ] Routing isn’t that all that important anyways

[ ] Benchmarks are more important than developer ease-of-use

Your framework won’t gain adoption because:

[ ] Your framework isn’t on Bower

[ ] Your framework isn’t on NPM

[ ] Your framework only works with a single module system

[ ] Your framework doesn’t work with any module system

[ ] Your framework is only for a language that compiles to JavaScript

[ ] Your framework requires an extremely specific back-end

Your framework doesn’t have working [ ] Grunt tasks [ ] Browserify transforms [ ] Require.js plugins

[ ] Your framework doesn’t have a starter kit

[ ] Your starter kit doesn’t actually let you create a production app

Your framework’s testing utilities:

[ ] Are undocumented

[ ] Are underdocumented

[ ] Require deep knowledge of the inner workings of the framework

[ ] Only work with a specific test framework

[ ] Don’t exist

Additionally, your documentation has the following flaws:

[ ] Your documentation is styled using unmodified Bootstrap

[ ] Your documentation is only an API reference

[ ] Your documentation lacks working examples

[ ] Your documentation is just your source code but with the comments on the side

[ ] Your documentation is a screencast

[ ] Your documentation is an example project

[ ] Said example project is a todos app

[ ] Your documentation requires a glossary and several open Wikipedia tabs for concepts in CS theory

Finally, your framework:

[ ] Poorly reimplements Angular’s dirty-checking

[ ] Poorly reimplements Ember’s router

[ ] Is basically just an event bus

[ ] Is basically just data binding

[ ] Is basically just web components, Angular directives, and/or Ember components

[ ] Does nothing that Ember or Angular doesn’t do better

[ ] Is a single, multi-thousand line file

(disclaimer: there is not a JavaScript framework in the world that doesn’t check some of the boxes above, and I have no particular dog in this race.)