Quintus
Quintus copied to clipboard
cykod
Upgrade to ES6?
The library is really awesome but I've noticed you guys are re-inventing the wheel in some places (for example, Q.Class.extend). Also, everything is a global which makes it hard to put classes in separate modules (files).
Have you guys thought about upgrading to ES6 or at least to AMD-style modules?
This could be interesting, indeed. But we would have to check the compatibility issues, as some browsers don't fully comply to the ES2015 norm. I'm sure some work-arounds exist, but will they be worth it? I'll let the others explain their points of view…
I think this would make absolutely sense for development. At the end as of now the whole thing will be transpiled to es5 anyways so we dont have any browser compatibility issues.
On 1 December 2015 at 09:35, Corentin H [email protected] wrote:
This could be interesting, indeed. But we would have to check the compatibility issues, as some browsers don't fully comply to the ES2015 norm. I'm sure some work-arounds exist, but will they be worth it? I'll let the others explain their points of view…
— Reply to this email directly or view it on GitHub https://github.com/cykod/Quintus/issues/172#issuecomment-160894023.
Agreed. Ideally we would write es6 classes and then transform our code into es5 using Babel in our build process.
fuck yeah!
On 13 December 2015 at 18:35, Alex Kinnee [email protected] wrote:
Agreed. Ideally we would write es6 classes and then transform our code into es5 using Babel in our build process.
— Reply to this email directly or view it on GitHub https://github.com/cykod/Quintus/issues/172#issuecomment-164279292.
Lemme know if you guys need help.I have experience migrating legacy code to systemjs/es6.In fact, I already have a demo quintus app using systemjs and es6
Thanks!Uriel AvalosLead Developer ConsultantChander Dhall, Inc
---- On Sun, 13 Dec 2015 11:35:29 -0600 [email protected] wrote ----Agreed. Ideally we would write es6 classes and then transform our code into es5 using Babel in our build process.
—Reply to this email directly or view it on GitHub.