I've been thinking recently that making a switch over to pure JS (EcmaScript 6) would be a better choice to help contributors get used with the codebase.
The idea is to keep the current API and port the CoffeeScript code over to ES6.
To make that possible we would need to use the popular tool called babel since ES6 support is not yet complete in the majority of the browsers we want to support.
It's important to cover this issues:
[x] It must be done in a specific branch and only merged when ready.
[ ] It must maintain the existent API, thus people using it right now won't notice the change when updating.
I've been thinking recently that making a switch over to pure JS (EcmaScript 6) would be a better choice to help contributors get used with the codebase.
The idea is to keep the current API and port the CoffeeScript code over to ES6.
To make that possible we would need to use the popular tool called babel since ES6 support is not yet complete in the majority of the browsers we want to support.
It's important to cover this issues:
grunt
tasks should remain the same.