Re:Bringing asm.js to the Chakra JavaScript engine in Window...
by quonn on Wednesday February 18, 2015 @04:04PM
(#9070924)
At least for Chakra, this would make a lot of sense - I can't think of a downside for them. For Trident there is the theoretical downside that IE becomes fully independent of Windows. This currently doesn't matter, but might decrease lock-in in the future.
[ Parent
| on HN ]
Re:Bringing asm.js to the Chakra JavaScript engine in Window...
by higherpurpose on Wednesday February 18, 2015 @04:07PM
(#9070946)
Windows dependency of IE is one of the worst things about IE - like having to restart your PC to update your browser. What year is this again?
Re:Bringing asm.js to the Chakra JavaScript engine in Window...
by integraton on Wednesday February 18, 2015 @04:13PM
(#9070981)
The fact that it was stagnant, ubiquitous, limited to Windows, and encouraged ActiveX were the major issues, since it made it more difficult and expensive to develop and transition to web applications for about a decade.
Re:Bringing asm.js to the Chakra JavaScript engine in Window...
by wmf on Wednesday February 18, 2015 @07:19PM
(#9071765)
Windows will automatically reboot every 6 weeks anyway once evergreen Windows 365 comes out.
Re:Bringing asm.js to the Chakra JavaScript engine in Window...
by MLR on Wednesday February 18, 2015 @04:58PM
(#9071239)
I've been thinking that Spartan will probably go cross platform at some point, an opportunity for them to get a few more Microsoft accounts created and it's not like it being Windows only is going to convince people to switch.