News for hackers. Stuff that matters.

A comment on JavaScript performance, WebAssembly, and Shared Memory in Microsoft Edge. Parent comment

Re:JavaScript performance, WebAssembly, and Shared Memory in... by bzbarsky on Saturday April 22, 2017 @12:33AM (#14171132)
> That's not really Chrome's fault

It's Chrome's fault that it's shipping non-standard things. Not like any browser is blameless here, but let's not pretend they're innocent either.

It's _Google's_ fault that it's shipping non-standard things in its browser and then using them in its other products to lock out other browsers.

> We didn't blame Microsoft for "lock-in" back in the IE-only website days

We sure did. And it wasn't even Microsoft creating the IE-only websites!

[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by sangnoir on Sunday April 23, 2017 @12:10PM (#14178729)
> It's Chrome's fault that it's shipping non-standard things.

I challenge you to name one non-niche browser that didn't ship "non-standard things"

[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by pcwalton on Sunday April 23, 2017 @01:16PM (#14179105)
The norms have been different in the past few years than during the first browser war. All browser manufacturers have effectively pledged to not ship things without consensus.

In the case of NaCl, Google got around their own pledge by declaring NaCl "not part of Blink" and therefore not subject to the Blink rules, which was a cop-out if I've ever seen one.

[ Parent | on HN ]
Re:JavaScript performance, WebAssembly, and Shared Memory in... by bzbarsky on Monday April 24, 2017 @02:48PM (#14186888)
I explicitly said other browsers have done it too.

Chrome has done a lot more promotion of its non-standard things and of course Google as a whole has been using Chrome's non-standard things quite a bit, which is a large part of the problem.

[ Parent | on HN ]