I have allready written tons of Dart code, and i have to admit there were a few issues with the JS-code regarding cross browser compatibilty (btw. it is easy to read the generated js-code). Those issues were problems in the dart2js compiler because it's a alpha-version right now. The dart2js team fixed all those bugs. As soon as the compiler will finally ship we will rely on the generated output - no need to debug "assembly language".
The constant is coming from the runtime library (or, more accurately, the portions of the runtime library that your program uses). That's relatively fixed so as your Dart program gets larger, the overhead of that becomes relatively smaller. The actual code-size multiplier when going from Dart -> JavaScript is actually fairly small and getting smaller over time.
In some cases, we may actually compile Dart code to less JavaScript code because of things like dead code elimination and constant folding.
JavaScript code size is something that we consider a core metric for dart2js and we're constantly working to reduce it.
JS has flaws, of course, but reacting by trying to make a completely different paradigm language that compiles to it seems a bit of an overreaction.