3 ms·
Good to see you here today, and glad to know that. Why ES2015 specifically? Like where are the compatibility issues or is this a necessary upgrade path for old
by vmception 6y ago
Good to see you here today, and glad to know that.
Why ES2015 specifically? Like where are the compatibility issues or is this a necessary upgrade path for older versions and then you’ll phase into es6 or leapfrog that to something even newer?
Or if ES2015 is “good enough”? Javascript can be a hot mess, there isn’t always a need to keep up and the troubles arise when you try to.
- harshitaneja 6y agoES2015 is ES6.
- vmception 6y agoThanks
- mbostock 6y agoCollections (Map and Set) and iterables; the latter practically requires for-of syntax and so can’t be supported in older browsers. d3.group and d3.rollup are much more enjoyable to use than d3.nest.
- vmception 6y agoIs this a consideration of many JS library maintainers? Or just you because D3 has broad appeal. This and other compatibility charts shows only Internet Explorer continuing to be the bane of your existence. https://kangax.github.io/compat-table/es6/ https://kangax.github.io/compat-table/es6/
- nicoburns 6y agoIE11 is still widely supported across a lot of the industry. It's use is declining, but I suspect it'll be a a good while yet before it disappears because there are still so many IE-only internal apps.