Hacker News new | ask | show | jobs
by oarabbus_ 2194 days ago
"It will break a lot of code"

Yes, because there's no precedent for non-essential changes which break code. Maybe there's a good reason not to change the "master/slave" terminology but this sure as hell ain't it.

1 comments

Once again, the usage here has nothing to do with master-slave idea. Obviously there is precedent for breaking changes. The benefits must outweigh the costs, the cost here is monumental, and the benefit here is non-existent.
>and the benefit here is non-existent.

To be clear, I'm not advocating for this change to occur. But clearly others disagree with you on this bit.