Remix.run Logo
▲ skybrian 5 hours ago

Yes, that's how you take separate causes and transmorgify them into one omnicause, by muddying the waters until you can't see the differences anymore. Don't do that! It just adds confusion.

(The same thing happened with separate company's problems becoming "Big Tech." It didn't help.)

▲xboxnolifes 4 hours ago | parent [-]

Once you give separate things a shared name they become the same thing. We could call those in the claim to be "race to the bottom effect" or "incentives against resiliance". The water is no longer muddled, its now a slushie.

▲AnimalMuppet 4 hours ago | parent [-]

You could call it "category theory" or something.

Snarky, but there's a point: Abstraction leads to viewing different things as the same thing. They are - at one level of abstraction. And they aren't at other levels of abstraction. It's not a problem to have both viewpoints.

The trick is that, when someone blends things together, to not lose the fact that they are also separate (at other levels of abstraction).

So I have no problem saying that "optimizing for efficiency and speed" is the common cause of all of these problems, and saying that they all have different (immediate) causes. Both can be true.

▲skybrian 4 hours ago | parent [-]

Sometimes these abstractions are useful for design or analysis, but maybe not for explaining them to others? A library or programming language will probably be more usable if its users don't need to know any category theory.

I'm not sure "optimizing for speed and efficiency" can count as a common cause, though, because it's not a single event. It's more like a set of events that have something in common.