trelonid

>In my experience though projects tend to start in a single crate, without great attention to their internal dependency graph, and once compilation time becomes an issue, they have already created a spaghetti dependency graph that is difficult to refactor into smaller crates.

Maybe there should be a lint for not having modules be mutually dependent?

I know this is silly, but I'm curious what you see. I see a man eaten by an elephant.

I've seen enough. Get the stake and the fire.

How do Linux Devs manage to not accidentally break device support constantly? I imagine this stuff is close to impossible to write automated tests for.

To be honest this article seems like a presentation, maybe someone else may find an impact it had as the author wasn't able to

What happened to "we have all the test kits we need"? This is why so many medical experts are screaming for an increase in testing capability.

>The exact ingredients vary from one coffin to the next, but the goo was always made from some of these ingredients

what I understand is that they didn't measure the ingredients, but rather put how much they thought was good

I think the answer is simple: the Advertising Business has very deep pocket and can interfere with such laws.