News for hackers. Stuff that matters.
Re:A horrifying globalThis polyfill in JavaScript by kozak on Monday May 13, 2019 @09:13AM (#19898891)
So, we made the polyfill horribly hideous in order to make it run everywhere JavaScript can run, and yet, it doesn't work on IE10-. Maybe it's not a good way to set globalThis after all :)
Re:A horrifying globalThis polyfill in JavaScript by folkrav on Monday May 13, 2019 @09:21AM (#19898959)
IE>11 is 0.35% of global usage according to caniuse, and even being generous and pushing it to 0.5%, it's horribly low. Maybe we just shouldn't support IE>11 anymore.
Re:A horrifying globalThis polyfill in JavaScript by TheCoelacanth on Monday May 13, 2019 @09:42AM (#19899110)
That's still much, much higher usage than jsvu[1] which they gave as the justification for needing this polyfill. 0.35% of Internet users is ~14 million people. jsvu has been on npm for about a year and has never had more than 1000 downloads per week, so it has under 50k users, more than two orders of magnitude less than IE<11.

[1] https://www.npmjs.com/package/jsvu

Re:A horrifying globalThis polyfill in JavaScript by mathias on Monday May 13, 2019 @02:13PM (#19902060)
Author of the referenced article here.

The article includes a working polyfill that includes old IE support, so I’m not sure what you’re complaining about.

Also, saying “jsvu is the justification for the polyfill” doesn’t make much sense. jsvu is just how I happen to test in various standalone JavaScript engines. There are other, non-jsvu ways of getting such binaries, e.g. compiling one yourself, and there are JS engine binaries that jsvu doesn’t provide (Rhino, Ringo, Nashorn). jsvu usage does not correspond to anything you seem to be talking about, and comparing its download count with IE10 usage is one of the more extreme apples-to-oranges comparison I’ve seen. ️

Re:A horrifying globalThis polyfill in JavaScript by chii on Monday May 13, 2019 @11:46AM (#19900451)
also, enterprises tend to have old tech stacks, forcing some business apps to continue to support IE10 (not even IE11 yet!)
Re:A horrifying globalThis polyfill in JavaScript by folkrav on Tuesday May 14, 2019 @09:24AM (#19909201)
I'm perfectly aware. Still doesn't really justify supporting a platform that has been out of support for 2.5 years now, with the security implications this has.
Re:A horrifying globalThis polyfill in JavaScript by mathias on Monday May 13, 2019 @02:13PM (#19902070)
The article includes a working polyfill that includes old IE support.