No, you changed the argument from correctness to performance. Makes me wonder if the problem is not entitled sloth with a dash of anti-JS animus, rather: whole

No, you changed the argument from correctness to performance. Makes me wonder if the problem is not entitled sloth with a dash of anti-JS animus, rather: wholesale, '90s-Microsoft-style-lock-in, submarine-the-other-browsers dirty pool. Of course, if dart2js produced too-slow-JS, that might limit Dart adoption. Not a dilemma, given a good-faith effort to optimize per my comment above -- and much better than forking the language between DartVM and dart2js, leaving a trap for the unwary Dart programmer to fall into when using dart2js to run on all the non-DartVM browsers. "Make it correct, then make it fast." Is this no longer done where you work? (Which would be Google, amirite? :-P) /be