4 ms·
>2) I wish they'd just give up on Turbolinks Ditto for Coffeescript. I realise you can't just remove it, but the whole dev community is raving about ES6 - ther
by technion 11y ago
>2) I wish they'd just give up on Turbolinks
Ditto for Coffeescript. I realise you can't just remove it, but the whole dev community is raving about ES6 - there's a whole of JS devs who could be a lot more interested in Rails.
- danmaz74 11y agoTurbolinks can create problems even to those who don't use them explicitly, but Coffeescript can't: if you don't like it, just don't use it, and it's as if it wasn't there. How would removing it from the asset compiler help you in any way?
- technion 11y agoThere's a cultural impact - it's hard to look at Rails without being pushed in that direction. Does it directly impact me now that I choose to ignore it? No. Does it impact a newcomer, particularly one that's into JS? Yes.
- KurtMueller 11y agoThis nifty web app is a good starting point: http://js2.coffee/ http://js2.coffee/ It's not perfect but it's how I learned coffeescript. Other than that, I don't think Rails necessarily pushes either for/against coffeescript. You can either use it or not. Plenty of rails apps have been written in plain 'ol js.
- KurtMueller 11y agoYou can choose to not use coffeescript in any Rails project. As for ES6, there is the sprockets-es6 gem. According to their github gem, their goal is to get in es6 support into sprockets 4. This, obviously, is not a perfect solution - but I think this is going in the right direction.