Hi, I have few questions regarding the
ecmascript package coming with 1.2 release of Meteor.
- Are you planning to rewrite most of the Meteor core to use ES2015?
- What advice do you have for developers creating packages in terms of using ES2015. In my two packages ReactiveMap and Astronomy I use some workarounds to support old browsers. In my situation, it’s defining setters and getters using
Object.definePropertymethod. As far as I know there is no polyfill for that feature. In the
ReactiveMappackage I’ve decided to replace
sizeproperty with the
size()method to make it reactive. In the astronomy package I’ve introduced the
Astro.config.supportLegacyBrowsersflag that changes the way Astronomy behaves. Should I support older browsers?
- In many new libraries, developers don’t care about old browsers. Let’s take PIXI.js 3.0 as an example. The authors use the
Object.definePropertymethod extensively and thanks to that they force people to use newer browsers. For how long are you planning to support old browsers? As a company that may change a lot in the Web, you should promote the newest standards. But by supporting old technologies we won’t move far away from where we are now.
- Do you have any feedback on how many developers want support for old browsers?