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-s
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 compatibilit
2 matches
Mail list logo
