I don't think that the industry has generally accepted that. It seems pretty hotly debated AFAICT. What is not debated much, AFAICT, is that it's much much ea

I don't think that the industry has generally accepted that. It seems pretty hotly debated AFAICT. What is not debated much, AFAICT, is that it's much much easier to work on large/old codebases when you have types. That's really where Rails runs into issues. But it's not like legacy rails monoliths start throwing NPE or other type errors everywhere. It's just that developer productivity grinds to a halt. Mostly for two reasons: (1) You have little idea where the code your modifying is used. Metaprogramming and indirection through send and constants make it hard to find every place it's called. (2) If you're the 5th function in the chain you have no idea where your parameters are coming from. So you have no idea what type they are and method autocompletion doesn't work. Especially annoying when things get complex and you end up with multiple similar but slightly different representations of things.