JavaScript performance, WebAssembly, and Shared Memory in Microsoft Edge

Re:JavaScript performance, WebAssembly, and Shared Memory in... by shurcooL on Thursday April 20, 2017 @04:35PM (#14160592)

People didn't like primarily because IE was fixed version, tied to operating system version, Windows-only.

Chrome is evergreen, cross platform, open source.

That makes a big difference. Chrome gets bug fixes, implements new standards, etc.

[ Parent | on HN ]

Re:JavaScript performance, WebAssembly, and Shared Memory in... by pcwalton on Thursday April 20, 2017 @04:39PM (#14160629)

When IE took over the market, it was implementing new features at a breakneck pace. The browser wars were not "IE sits still and gains market share"--they were "IE develops rapidly, takes over the market, and then stops development".

[ Parent | on HN ]

Re:JavaScript performance, WebAssembly, and Shared Memory in... by hashhar on Thursday April 20, 2017 @06:51PM (#14161599)

AJAX, bi-directional text, most conformant CSS 2.0 browser, border-box sizing CSS model are all things where IE was ahead of the times. The reason people hated IE was because it implemented only "just enough" to get ahead and then sat on their asses until someone catched up. That's where the antitrust came from.

[ Parent | on HN ]

Re:JavaScript performance, WebAssembly, and Shared Memory in... by blackoil on Thursday April 20, 2017 @09:15PM (#14162326)

I believe, order is reverse. IE team was dismantled after the antitrust suit.

[ Parent | on HN ]

Re:JavaScript performance, WebAssembly, and Shared Memory in... by zp-j on Friday April 21, 2017 @03:54AM (#14163789)

Sorry, Chrome is not open-sourced, Chromium is.

[ Parent | on HN ]

Re:JavaScript performance, WebAssembly, and Shared Memory in... by shurcooL on Tuesday April 25, 2017 @07:03PM (#14199006)

That is a valid point, thank you for bringing it up.

[ Parent | on HN ]