That just means you must make more than one cut to isolate the segment you're working on, or you have to get your splice in while the trucks are on the way to the decoy cut.

Unfortunately, in this case the pain spreads around. The sluggard isn't necessary the one who suffers for it.

ISPs get stuck dealing with NAT because too many servers are only reachable via v4, servers get stuck scrounging v4 addresses (possibly at great expense) because too many ISPs don't support v6, etc.

You've obviously never worked on an embedded system. Sometimes in that space, you throw out absolutely anything and everything you don't absolutely positively have to include. That's why busybox exists and has a config menu that lets you choose exactly what commands to support. Likewise, dietlibc for when glibc is too big.

A simple firewall rule will provide all of the security NAT would provide and with a lower load on the firewall.

Just enable connection tracking, accept incoming related packets and drop the rest.

That was IANA running out of blocks to hand out to the RIRs such as ARIN.

Now, since it can't get any more, ARIN has also run out. The remainder are held by corporations and individuals and they have no obligation to hand them over.

Perhaps all of that was an attempt to motivate at least a lukewarm response to the obviously coming problem so people wouldn't end up running around with their hair on fire later.

No, it wasn't. It was predicted that IANA would soon run out of blocks to hand out to the regional registries unless allocation policies were tightened up. They were tightened, but in spite of that, it ran out in 2011. IANA was last predicted to ruin out on July 5th this year. They almost made it.

For that reason, only Africa has addresses to hand out now, but that will be exhausted in just a couple years.

I am aware that it can be taken out of the driver's seat (I do so every time), but I am also aware that doing so doesn't remove the dependencies on the libraries and that the systemd team is hard at work removing even that option.

You should try looking at the other pages, there's more than one there.

Meanwhile, if you think Jessie doesn't use systemd, you clearly haven't been paying attention to that either.

No, it exploded because an edict to run the test came down from on-high and heads would roll if it was delayed. So, to get things done within the deadline, it was assigned to the poorly trained night operators rather than the better skilled day operators. Then they did every don't in the book to avoid having to report failure after making a mistake. It was that final mistake of withdrawing all of the control rods trying to burn off the xenon poisoning that made it blow.

Yes, they just hate it when we keep them sorta-kinda semi honistish.

So you're saying all those messages I get from the mailing list are a hallucination?

Sorry no.

I recognize that things have become skewed and enforcement is incredibly lax these days, but first and foremost, a corporate charter is contingent on the existence of the corporation being in the public interest. There is no such thing as a corporation's natural right to exist, it is a creation of the state (and by extension, the people). But for vast amounts of money and corruption, a corporation that continues to break the law would be denied existence (as it isn't in the public interest to create criminals).

They are certainly NOT required to lie and cheat at all. They choose to do so, but it is far from required. Flooding the market with liars and cheaters is not in the public interest at all. The market only functions well where there is fair dealing (or at least the courts and law enforcement impose fair dealing).