5 ms·
You're forgetting the period of Ruby's popularity in the devops world, especially Chef and Puppet.
by cutler 3y ago
You're forgetting the period of Ruby's popularity in the devops world, especially Chef and Puppet.
- local_person 3y ago[dead]
- rcarmo 3y agoPuppet was pretty awesome. We used it to maintain and provision nearly every kind of software across a few thousand machines, even though it had a worrying tendency to remove user accounts (we once got locked out of the master...)
- moonchrome 3y agoI think that's just building on RoR hype in that same field. Puppet even moved away from Ruby AFAIK.
- cutler 3y agoI beg to differ. Most sysadmins I knew who used Ruby extensively had never touched Rails. There's no real connection between the two phenomena other than the language.
- raziel2p 3y agoPuppet was just built with Ruby (and later re-written, I think?), in all my years interacting with it I never actually wrote any Ruby. Chef you obviously had to, but my impression is that the DSL is so extensive you might as well be writing something that's not Ruby. Maybe this says something about the power of Ruby, but I don't feel like these tools contributed to the language's popularity or ecosystem - definitely not the way RoR did.
- lolinder 3y ago> my impression is that the DSL is so extensive you might as well be writing something that's not Ruby. This is just how Ruby is. It's designed around the idea of building DSLs, so writing in Ruby is almost always an exercise in writing in one DSL or another.
- cvak 3y agoI've spent year and a half writing chef as my first "programming" job, like 6 years ago. I learned almost 0 ruby, and that's probably why ruby didn't stick that much.
- lolinder 3y agoYeah, I suspect this might be one reason why Ruby hasn't gained as much traction as others: knowledge doesn't translate well between frameworks, so there's little advantage to re-using the same language for a new project (unless it's a new project in the framework you're already comfortable with).