4 ms·
> then became universally relied upon but somehow never enabled by default. Often it's not that universal; especially for older software there's a lot of varie
by arp242 3y ago
> then became universally relied upon but somehow never enabled by default.
Often it's not that universal; especially for older software there's a lot of variety in how people use it, and changing defaults can be hugely confusing for existing users. A lot of these (alleged) "don't suck" buttons are probably more subjective than you might think.
The HDMI thing may be a security-related, or maybe there are is another reason. I think it's important to know why something behaves as it does, without too quickly assuming there's no good reason for it. That's also my criticism of this submission by the way: it makes little to not effort to understand why things are as they are.
- chii 3y agoThis is the chesterton's fence. Don't remove the barrier until you understood why the barrier was there first.
- worthless-trash 3y agoThank you ! I for some reason tried googling this word last week and had "gate" stuck in my mind.
- johnnyanmac 3y agoagreed. It's one of the most painful parts of legacy code, especially when left 10 years ago by an engineer who has long departed the company that just says "DO NOT CHANGE" (or something to that effect). A beginner sees incompetency, while an expert can already imagine the war stories, the politics, the potential crunch and desperation, and the weeks of demonic bugs fought to warrant such a comment. (Or you know, you dig a bit and find a thinly documented fix to that issue from 5 years ago).