On Saturday, 29 June 2013 at 09:08, teramako wrote:
> I would want Mozilla to fix those issues rather than implementing new
> methods of ES.next and keep the top engine which has the most
> compatibility for ECMAScript.
I didn't quite get the rationale for why we should fix stuff that's
non-standard instead of putting energy into the ES.next? Won't fixing
non-standards things just encourage people to use it more and lead to more
confusion/content (thus making it harder to do away with the non-standard
stuff)?
--
Marcos Caceres
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
