Open Stack

ES6 is risk-free solution. Browsers do not support it properly, but it is
not a problem. ES6 code can be compiled to ES5 and be used in browsers
until proper ES6 support appear. Fuel uses Babel (https://babeljs.io/) to
compile ES6 to ES5. Node 6.x supports it almost completely.

Anton

On Tue, May 3, 2016 at 9:42 PM, Michael Krotscheck <krotscheck at gmail.com>
wrote:

> TL/DR: Should we support EcmaScript 6?
>
> Discussions I've had on the topic:
>
> Vancouver:
> - Browser support is not yet broad enough, so no- we shouldn't support
> ES6.
> - TypeScript is too closely tied to Corporations (tm), not really an open
> standard. Do not support TypeScript.
>
> Austin:
> - Fuel is using ES6, is now an official project (?).
> - We have non-browser projects that could use it, assuming that we have a
> recent version of Node.js that we can test on.
> - We now have Node4 LTS on our infra build nodes, which support _most_ of
> EcmaScript 6 things.
> - EcmaScript continues to be moving target (And will likely always be a
> moving target).
> - Xenial contains Node 4 LTS. Ubuntu does _not_ have an upgrade exception
> for node (akin to Firefox).
> - Node 6 LTS was released during the summit.
>
> Body of work required:
> - Discuss and enable linting rules for ES6 in eslint-config-openstack.
> - Smoke-test fuel's unit and functional testing for ES6 components.
>
> Personal Assessment:
>
> Frankly, we already have ES6 in our infra, so that train has left the
> building. What we need to do is make sure it has the same level of support
> as other languages, which, I believe, isn't going to be too difficult. I
> also have some commitments of mutual assistance from Vitaly (Fuel) to keep
> things sane and keep communication open. As for the upcoming Node4 vs.
> Node6 question, I recommend that we _not_ upgrade to Node 6 LTS in the
> Newton cycle, however strongly consider it for the Ocata cycle.
>
> Am I missing anything? Does anyone have opinions?
>
> Michael
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160511/eec1ee27/attachment.html>