interdependent

But the point in the article is no effect is without a cause, and there are interdependent causes.

> But the point in the article is no effect is without a cause, and there are interdependent causes.

If nothing else, this implausible plans makes me think how interdependent and hard-to-simulate a real, working city is.

An massive integrated, interdependent industry can't be plausibly compared to the motley collection of itinerant farmers roaming America in 1900.

Given a set of tasks T, that have to be done, and the tasks are interdependent.

Work culture is not about the worker or the work anymore, it is about creating an interdependent unit of labor.

Once you have a real system, heavily interdependent, the cost of changing things starts to go up greatly, and your ability to cleanly describe a working system becomes challenging.

My recollection is that they let it twist in the wind because SaaS competed with their two interdependent quasi-monopolies: Windows and Office.

I think the node_modules directory structure is a novel, though straightforward, solution to the problem of interdependent module versioning.

Right now it's very noisy, presumably because the frames aren't really interdependent.

They've offered Shumway as an interdependent re-implementation, but I'm guessing it has tons of compatibility issues as Flash isn't a standard.

Adding technical barriers is one thing, suing and interdependent group of people trying to learn the API and building tools on top is completely unfair.

A common argument is to insist that breaking up systemd into a separate binaries made "not monolithic", while ignoring that the design is still totally interdependent.

Someone realized that thread safety was actually two, intertwined and interdependent concepts -- thread safe and share-safe[^1], and together they allowed for a good degree of safety without being too restrictive (unlike just having "non threadsafe" types).

Because of this, the ops team needs to be involved in keeping the VM up to date, the VM usually needs to be "managed" with orchestration much like a physical machine, and all-in-all it's big interdependent mess where the devs can't just forget about deploy-time concerns.

> they let it twist in the wind because SaaS competed with their two interdependent quasi-monopolies It wasn't called SaaS back then, but in any case -- they let it "twist in the wind" because their market had become the enterprise, and that's a market that wants stability, predictability and no updates if they can be avoided.