You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realize this is not urgent and the package works as is, but I think the recommended way to create atom packages now is to use JavaScript/ES6 instead of CoffeeScript. Having the code in JS instead of CS has the advantage that many more people are familiar with JS than with CS (my case), besides the other network effects of using a more popular language. Also ES6 incorporated many of the improvements brought by CS.
As a way to familiarize myself with the code I'm willing to convert it to JS and send PRs, but only if the maintainers are interested in this conversion.
The text was updated successfully, but these errors were encountered:
Gah, javascript is so much less fun than coffeescript... 😝
This seems inevitable, but right now is not a great time, as I have a fairly busy branch implementing isearch right now (feel free to try it!). Perhaps after that's merged?
I realize this is not urgent and the package works as is, but I think the recommended way to create atom packages now is to use JavaScript/ES6 instead of CoffeeScript. Having the code in JS instead of CS has the advantage that many more people are familiar with JS than with CS (my case), besides the other network effects of using a more popular language. Also ES6 incorporated many of the improvements brought by CS.
As a way to familiarize myself with the code I'm willing to convert it to JS and send PRs, but only if the maintainers are interested in this conversion.
The text was updated successfully, but these errors were encountered: