Some languages and ecosystems can be more helpful, though, even if none can save you. Rails is memorization-heavy and doesn't have static types to aid in navigation & reading. Its runtime auto-magic even resists grepping. Auto-imports mean you don't even get a decent list of which sources are contributing to a given file's behavior.
It's also the case that different teams can write it pretty differently, depending on gem choices and which Rails features they lean on. Plenty of other languages and ecosystems are like that, too, but all the above stuff means Rails is exceptionally bad, in that regard.
corrral|3 years ago
It's also the case that different teams can write it pretty differently, depending on gem choices and which Rails features they lean on. Plenty of other languages and ecosystems are like that, too, but all the above stuff means Rails is exceptionally bad, in that regard.
jshen|3 years ago
The worst code bases I’ve worked on used statically typed Java.
Lio|3 years ago
Except of course that now it does.
So worst case if you inherit a codebase without static types added you can use gradual type as you get to know it.
fomine3|3 years ago
nine_k|3 years ago
[1]: https://data.whicdn.com/images/198477032/original.jpg