>But before I did so I researched first. I asked a few instances to analyse the project in terms of gains of complexity, stability, testability, etc., and while (obviously) stability would drop (no types in Ruby) it’s not that awful (Sorbet has types in Ruby!).

Is it not a rage-bait argument to say that not having types implies less stability?

No? Maybe the industry can now talk maturely about tradeoffs like that rather than pretending they don't exist.