I have a love hate relationship with rails. I think rails is quite powerful and great for prototyping. But I’ve noticed lots of rails developers optimize so heavily for making things DRY, they make the most hard to debug monstrosities full of meta programming all so they could write a thing one one line of code instead of 3. Still for starting out it’s pretty awesome. If your company grows enough that you have legacy…
> I’ve noticed lots of rails developers optimize so heavily for making things DRY, they make the most hard to debug monstrosities full of meta programming all so they could write a thing one one line of code instead of 3. I think that was definitely the case some years ago, but the Ruby community has matured since then. Meta programming is a bit looked down upon, these days.
I still see a false equivalency in the ruby community that verbosity == complexity, that tends to make super complex abstractions and DSLs in order to make the consumption less verbose, that then say “see how simple this is to use”
Because rails does such a good job in their DSL, I think I understand why that tendency exists. But rails under the hood is quite complex, and most DSLs are no where near as well thought out.
Maybe I have Stockholm syndrome, because I hated ruby coming from a nearly all c style language background at first, but I honestly think it is pretty cool now. I think a lot of issues come from people wanting to do things in ruby like they would in C# or Java.