3 ms·

Thanks for the insight into Elastic Beanstalk; I'm looking into it now. Regarding Coffeescript and classes, I think that's a really poor reason to use it. IMO

Thanks for the insight into Elastic Beanstalk; I'm looking into it now. Regarding Coffeescript and classes, I think that's a really poor reason to use it. IMO Coffeescript has had its day and if you want class sugar, just use ES6. You're already using a compilation step in your process so why not use it to work with something standard?

tn6o 11y ago
You're probably right indeed! I was just looking into refactoring some code, found that and thought it was pretty cool. Plus Rails comes with CoffeeScript by default. ES6 is pretty sweet (pun intended) and will probably make CS kinda useless in the future. I'll look into it however I think that currently CoffeeScript is a bit of a standard in the Rails world.
- colinramsay 11y ago
  That is a fair point, if I'm using Rails I actually just use plain old JS as I don't personally like CS. I just found a comment by a Rails contributor [1] which says ES6 will be supported out of the box in Rails 5, which would be ideal. I can't find anything newer to back that up though. I think it might be via ES6 support baked into sprockets. [1] http://kryptonlabs.com/blog/2015/10/25/whats-new-in-rails-5/#comment-2326469442 http://kryptonlabs.com/blog/2015/10/25/whats-new-in-rails-5/...