Doing fiddly Ruby stuff for a Nanoc iteration of the site.
-
Doing fiddly Ruby stuff for a Nanoc iteration of the site. My frustration persists that more than 80% of the answers to "how do you do X in Ruby?" are "use this Rails package."
It's a major contributor to falling out of love with Ruby over a decade ago. Not the language, but the widespread assumption of a monoculture.
Hanami, TTY Toolkit, dry-rb, Nanoc. There's cool stuff out there!
Also I don't like Rails.
-
@randomgeek I hear you so much on this. I'm back in Rails land after mostly doing SRE/infra for the past several years and I still see why folks like it (and why I used to), but the chokehold it has on Ruby is really discouraging.
-
@jamie the most neutral thing I can say about Rails: I respect and appreciate that it is a highly opinionated framework. I just share few if any of its opinions.
But I could fake it pretty well if a steady paycheck was involved.
-
@randomgeek This is very solidly neutral, well done! I don't know that I could've been as neutral, tbh.
The thing that bothers me the most about it is that even though I like certain aspects of Rails, I don't think it encourages good software development.
-
@jamie It definitely hasn't in the Ruby world, that's for sure. There was a healthy discussion going about the benefits and shortcomings of monkeypatching, as well as establishing DSLs vs APIs and the semantic differences between them.
Then Rails jumped all-in on the cutest shortcuts they could come up with, called it "convention over configuration," and routinely denigrated practices aimed at software quality.
That a functional ecosystem managed to evolve around that is the real miracle.
But that's me, holding a grudge since uh when did the first pre-1.0 blog showcase video come out?
I'm sure some of my bias is there just out of habit at this point.
-
@jamie I looked it up and yeah my grudge somehow predates the blog showcase video.
Sometime after 0.1 but before 1.0, grumbling about how it was aiming to be an everything Web framework, and taking the shortest path possible to every point.
But I've always been maybe not into microservices, but at least focused services. So that's the aesthetic that got rubbed wrong early.
Again me vs Rails in short: strong opinions, not shared.
