I agree with this take. I work at Shopify using Sorbet and Rails. On a monolithic code base it can be very helpful to know what type is going to be returned.
On a smaller code base I may not bother with it for the reasons the original commenter mentioned.
Does it still feel like Ruby though or is it a new beast? I mean Typescript doesn't really look like Javascript at all and your whole mindset changes when you use it.
So is Shopify now typing the whole monolith ?
IMO it depends on what part of the ruby feel you most enjoy. Sorbet makes it harder to work with the runtime-magic parts of Ruby (and in some cases we rely on tooling-generated code instead of runtime dynamic stuff), but it doesn’t affect the code you’d write within methods all that much.
On a smaller code base I may not bother with it for the reasons the original commenter mentioned.