I posted to my blog:

SpiderMonkey Regrets - hogehoge
http://d.hatena.ne.jp/teramako/20130628/p1

I know SpiderMonkey is improving and new methods and statement are implemnted every day. I'm loving in these implementations. But SpiderMonkey has a lot of negative heritage about compatibility for ECMAScript6th.

Negative heritage:
 - non block scoped ConstDeclaration
 - mismatch GeneratorFunction syntax
 - mismatch ArrayComplehension and GeneratorComplehension sytax
 - "__iterator__" and "iterator" magic properties

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.

Best regards.
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to