These are chat archives for waterlock/waterlock

Dec 2015
Mehdi Aïssani
Dec 29 2015 10:18
@tjwebb Look at those functionality tables. Even if node4 is LTS etc... if the implementation of ES6 is not full, you may have not access on all ES6 functions yet or some functions will be change along the ES6 implementation, so there is a risk of unstability when coding on ES6 at the moment.
I agree with you about use ES6 but not for a framework at the moment because of engines that don't support it at 100%.
You can create it, develop it, making it grow but, don't ask people to put it on production for the moment.
I love SAILS and I love ES6, i think your project will have a future, i will watch it closely and as soon as node4 will be at 100% of implementations , I will use your framework, making some proof of concept and enjoy it.
Travis Webb
Dec 29 2015 17:28
@maissani difference of opinion. no one will support 100.00% es6 natively for years. that doesn't mean you can't start taking advantage of it now. the features in node4 won't change.
and we have dozens of es6 applications running in production. so do many large companies (some of whom are our clients). I'm perfectly happy to recommend running es6 in production. it's not some experimental draft anymore, it is javascript.