Just replace 'DSL' with 'API' in your comment and it describes using any large software framework. When you use on a framework to multiply your effort, you inevitably have to learn the ins and outs of the framework. In Ruby/Rails this is accomplished with a lot of class methods, but in other languages you would just be doing the same thing with instance methods or whatever.

Correct, but the key part I mentioned was "Given Ruby's lack of static typing". It's nearly impossible to hunt down source code in large Ruby projects due to mix-ins, dynamically adding methods to types, etc. At least in Ktor I've reasonably able to track down the implementations of most DSLs I've come across since it's statically typed. I tried the same in Rails long ago and gave up.

> Everything being a DSL is the worst part for me.

This is the worst part for me. Even though I've been using Rails for years, I still stumble on this.