Something internal that doesnt need to be understood can usually just not be written in the kinds of organizations I'm familiar with. Writing because something written is required is usually for the public, cross-organizational or government.

Removing equally frequent measures of normal by leaving enforcement checks to discretion is basically a method to create a biased system to target anyone who is suspicious to any authority and confirm every authority with arbitrary biases is a really good judge of character.

All of these concerns, even #1, have applied to communist car driving America and its 25% theft of everything..

I would tax the beejesus out of energy use and personal road use and invert most income tax to make something closer to a free market than the US is.

That's a strange way to put it. What teems with more life than an open sewer?

If I am not mistaken on my history, the NY sewers were the long time home to the Teenage Mutant Ninja Turtles

It depends on the sewage. Even bacteria die if there is lots of chemical waste innit, which was the case for a lot of so called open sewers.

It's life Jim, but not as we want it.

Reminds me of a Terry Pratchett quip about looking at the microbes in the drinking water in Ankh Morpork, along the lines of anything that could support that much life had to be healthy

Yeah, the article is good, but that headline had Onion qualities :)

Not all life is equal.

I think people who tell you it is 19th century live in countries that use IBAN/SWIFT to push money instead of checks to tell people an account is available to drain.

These countries also usually have bank-supplied or sponsored mobile payment apps (like Vipps in Norway) where the usual fraud protection applies.

That the US is 30 years behind the times in banking is not a shock but still stupid.

The other explanation would more likely be paying lawyers. The fact that one has money from thin air for lawyers can not be challenged in court.

I agree that suckless has a presentation problem in the workplace and the small things being hard are often working against you.

I don't agree that you should spend time configuring and suckless makes configuration hard on purpose. I think the suckless philosophy embrasses vi over the embarrassing plugin/configuration hellscape of vim.

IBM was the other offer on the table. Scott managed to scuttle the deal but his ability to do so was far from a certainty since he was already out as CEO.

Google was pretty much incompatible, they had no interest in workstations or paying for quality as their focus was redundant arrays on inexpensive machines.

Fujitsu was the best actual option for commercial compatibility, but everyone felt it would be a waste of time to pursue that as the USG would almost certainly block a foreign sale.

Google bought Motorola, amd that went okay until Samsung blew its top. Recall this was the era Google was frantically buying IP to shore up it's patent portfolio. Apple had gone "thermonuclear", so a somewhat-independent Google-ow ned Sun was in the realm of possibility,perhaps to be sold piecemeal.

Those patent wars were largely over wireless patents which Motorola had a lot of and Sun… didn’t.

Although Sun and Fujitsu had a long-standing business and development relationship, I think it would also have been problematic from a strategy and cultural perspective. My observation with the 3 big Japanese computer companies (NEC and Hitachi being the others) in the 2000s is that they aspired to be major global computer system suppliers--but weren't willing to actually make the investments to make such a thing possible.

I didn't think at the time that IBM was a good fit. I'm not so sure now in retrospect--though they would have had to rationalize the Unix business in particular.

The convenience of offering to re-login if your session is expired and you hit a site where you use it?

That could have been cached locally on your machine, separate from your vault.

It's certainly very interesting since Java was among the few high level languages that had unlimited access to C OS devs in theory, but it doesn't show this in practice.

I always felt they were hostile to understanding OSes and problems/solutions they provide and thereby limiting themselves to mostly junior C devs who didn't rock the boat by making real OS features for the JVM.