News for hackers. Stuff that matters.
Re:When Should You Not Use Rails? by brazzy on Wednesday August 05, 2020 @06:28AM (#24059151)
It's not really about trust, not even about skill.

I submit that this sentence:

> Ruby allows for a lot of non-local effects. Whether that’s monkeypatching, writing to a database or creating new types at runtime, Ruby isn’t designed for a team of 200 programmers

can and should end there, full stop.

The bigger your team, no matter how skilled, the more often someone somewhere will make a mistake and cause side effects they didn't intend. And when these side effects can manifest in unfathomable and hard-to-analyze errors in a completely different part of the codebase, you're in trouble.

Obviously, this can happen in any language, but some enable it a lot more than others, and some make analyzing weird behaviour a lot easier than others.

There are no comments on this comment yet.