4 ms·
Who'd have though that the first vendor to build in support for ES6 modules was going to be Microsoft? Of course it will be at least 10 years before people can
by pilif 10y ago
Who'd have though that the first vendor to build in support for ES6 modules was going to be Microsoft?
Of course it will be at least 10 years before people can safely require Edge and another 5 years before that version of Edge current enough to support modules.
Remember: IE11 will be supported with Windows 8, 8.1 and 10 until at least 2020 and the enterprise version of Windows 10 never gets feature updates and thus never an updated Edge.
- GlitchMr 10y agoEnterprise LTSB (as opposed to just Enterprise) is least of your problems, it's a niche Windows release, not supposed to be used by end-users, but rather by systems like kiosks, ATMs, medical devices, and other devices that shouldn't break, and doesn't need new features in an operating system. I doubt many LTSB browsers browse the internet (beyond perhaps having a website open in kiosk mode disallowing entering other websites), and even if they do, not with IE.
- toomanythings2 10y agoWasn't the announcement, yesterday, that webkit/Safari had complete implementation?
- madeofpalk 10y agoThe catch is there's the JS Module syntax, controlled by TC39, which WebKit may or may not support (not sure whether its a part of ES6 or not), and then there's the browser module loading standard, which is controlled by WHATWG.