Sick of Ruby, dynamic typing, side effects, and object-orientation (2014)

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by steveklabnik on Tuesday November 07, 2017 @05:20AM (#15642199)

Rails doesn't rely on CoffeeScript. It includes support for it by default, but you don't have to use it, and you can never start using it by passing a flag to `rails new` or removing the `coffee-rails` gem from your Gemfile.

[ Parent | on HN ]

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by mercer on Tuesday November 07, 2017 @06:18AM (#15642458)

How do the default affect the ecosystem these days, though? I remember back when I used Rails and CoffeeScript was the standard, it took a bit of work to avoid it altogether. This wasn't difficult, to be fair, but it felt like pointless busywork nonetheless.

[ Parent | on HN ]

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by rickyc091 on Tuesday November 07, 2017 @08:17AM (#15643069)

jQuery was removed in the latest version of Rails in favor of rails-ujs, essentially a vanilla js version of jQuery so `remote: true` and things like that would still work.

Erb / vanilla js is still the default stack for beginners. But they've started to move away from the asset pipeline and they've built in webpack.

[ Parent | on HN ]

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by steveklabnik on Tuesday November 07, 2017 @06:37AM (#15642526)

I couldn't tell you, as I haven't been really involved in Rails for a while. I never used coffeescript for any serious project, even when this change was made back in 3.1, and I can't remember it ever causing trouble. YMMV.

[ Parent | on HN ]