The language is incredibly flexible and allows for "DSLs" that are just ruby libraries. A simple example: `3.days.ago` is a very commonly used idiom in Rails p

The language is incredibly flexible and allows for "DSLs" that are just ruby libraries. A simple example: `3.days.ago` is a very commonly used idiom in Rails projects. Under the hood, it extends the base Number class with `def days` to produce a duration and then extends duration with `def ago` to apply the duration to the current time. Taking that concept to a bigger extreme is this mostly unnecessary library: https://github.com/sshaw/yymmdd https://github.com/sshaw/yymmdd `yyyy-mm-dd(datestr)` will parse a date str that matches yyyy-mm-dd format. It looks like a special DSL, but it's just Ruby. `dd(datestr)` produces a `DatePart`. Then it's just operator overloading on subtraction to capture the rest of the format and return the parsed date. That library feels unnecessary, but the entire thing is 100 lines of code. The ease of bending the language to fit a use case led to a very rich ecosystem. The challenge is consistency and predictability, especially with a large team.