3 ms·
The point is valid though. Yes Rails is particularly bad, but I've been working with Ruby for ~15 years now, and plenty of non-rails codebases in that time. The
by heeton 3y ago
The point is valid though. Yes Rails is particularly bad, but I've been working with Ruby for ~15 years now, and plenty of non-rails codebases in that time. The metaprogramming and implicitness runs deep in most of the community, it's common to find highly magic and hidden implementations in Ruby generally.
- rezonant 3y agoI often find the sort of over-the-top implementations you describe in gems that were written by Rails users. Since other frameworks and vanilla are not super uncommon, it's fairly normal to make your gem that you envisioned being used within a Rails app not dependent on Rails. If those developers read too much Rails framework code (or toxic blog posts from DHH) and got the wrong idea, then it's not surprising they imitated what they thought was the way to do things.