Now I'm quite sure you've never done any embedded work. Debian USED to be a good base for an embedded system.

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.

I state up front that I work on my own terms. I have talent to offer and can solve problems that others often can't, but I place a premium on flexibility and on my own health and family. I am incredibly productive, more than many other employees, but I do not offer *maximum productivity*, i.e. "as much as I am humanly able to produce." Even if it seems that I have more to offer (i.e. I leave at 6:30 when everyone else is still working and Skyping me at 11:30 pm, I travel a only couple of times per year and decline to travel 20 times per year, etc.), I am not willing to give this "more" to the organization—it is for my family and my own personal growth.

And both of the phrases I used are things I've been told—"We have doubts about your how serious you are; we're interested in someone that's more serious about their career" and "We don't doubt that you're highly skilled and productive, your resume and recommendations are stellar, but we're in a competitive industry and we need highly competitive people, and we're not sure you've got that competitive fire in your belly—that you're really going to be one hundred percent invested in the company and its growth."

I have two friends that have been on the serial startup carousel as founders. Both burned out and moved in other directions because they felt it was impossible to actually have a life, be a human being, and get growth and operating capital support from investors. Each startup became their entire lives each time until positive exit, and at some point each said, "I'm not doing this again, I'm losing my own sense of identity and my family."

And if you take that kind of statement out into the public sphere, I'd bet that what others would say is, "Well, they weren't really made to be enterpreneurs, then; they were destined to burn out because it's not the lifestyle for them."

Which is precisely my point—and it sounds like you've seen it, too—there's a prevailing "wisdom" that "real" career builders or "real" enterpreneurs are a particular "type"—the type that gives every . last . drop . of . blood to the company. The rest? They're just not "cut out for it"—they should "do something else."

Of course, if you're not "cut out" for the job market or for enterpreneurship, it's not quite clear what "else" you ought to be doing to earn a living. There are only so many jobs at nonprofits and in government agencies.

It would be better if society were to take a step back and assume the opposite—that everyone is basically loyal, driven, and productive, but in general, a healthy person cannot exist without healthy hours, life balance, and relationships, and if someone is the "type" to be working from 4:00 am until midnight every day of the week, and double that on holidays to pick up the slack, the are probably in need of counseling or personal development, rather than a raise and a promotion. But I suppose that's not how the market works.

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.

Umm. Yeah.

And why would someone writing GPL software care about that?