Explicit language might modify what would otherwise be there only by an implicit doctrine.

In general, a licensor can modify their own terms. So, if you are using the GPL on software to which you hold the copyright, and you add some sort of exception, it applies. You can't do it to other people's software.

I am still having a little trouble with "we don't need our spies to spy". Maybe we do.

I am also having trouble believing that the kind of encryption we use on the Internet actually stops the U.S. Government from finding out whatever it wishes although IETF and sysadmins might be kidding themselves that it can. Government can get to the end systems. They can subborn your staff. Etc.

MS language is potentially worse than the default. And there is room for litigation to surprise us.

Yes. The last stuff I wrote that I couldn't compile today was in "Promal" or "Paradox". My C and C++ code from 1980 still builds and runs.

All of my web development is on Ruby on Rails. That environment has had a lot of development and I've had to port to new versions. So old code for RoR would not quite run out of the box, but it's close.

Popular computing languages do not in general have only one Open Source implementation, and do not get abandoned.

Development with a proprietary language is ultimately harmful to your own interests, whether you make proprietary software for a profit or Free software.

The one thing every business needs is control. When you make it possible for another company to block your business, you lose control. Your options become limited. Solving business problems potentially becomes very costly, involving a complete rewrite.

The one thing that should be abundantly clear to everyone by now is that making your business dependent on Microsoft anything is ultimately a losing proposition. They have a long history of deprecating their own products after customers have built products upon them.

All Open Source licenses come with an implicit patent grant, it's an exhaustion doctrine in equitable law.

The problem is not patent holders who contribute to the code, you're protected from them. It's trolls who make no contribution and then sue.

Of course these same trolls sue regarding proprietary code as well.

Incident response: you're done as soon as you restore his access. The higher-ups made the call to keep him working for the next two weeks. It is not your place to countermand of interfere with that decision. If they wanted his access cancelled, they would have sent him home. Every minute he loses to your behavior is another bit of knowledge that doesn't get transferred to the next guy.

Long term: You have serious problems to address with your backups and business continuity planning. How do I know? Because if your backups were in order you wouldn't have asked. You'd know that you can readily undo any damage the guy might cause.

Compared to how the C-based kernel handles its byte buffers after you've written to the file handle? You really need help understanding how java strings are overweight _by comparison_?

They tested using strings in python and java, both of whose string libraries are very much overweight. And they tested by concatinating strings in a way that requires constant reallocations and memory copies versus pushing data to fixed size disk buffers in the OS cache.

So... surprise! When writing data sequentially the C implementation of disk buffers is faster than the java and python implementations of strings.

No! You're only allowed to worry about one or the other!

Really? If only there was some one out at sea on a boat who could corroborate that. . .

http://www.internationalpolicy...

Anything that becomes molten will mix into the fuel and dilute it,

Not really. Anything that becomes molten, will pretty much vaporize, because Uranium melts at like 2000 F. If the Uranium is molten, everything else will boil away.

However: It's bollocks because the hole in which the uranium is burning, has fissures and crevases, and the Uranium would unevenly flow into small, tight spaces, spreading out and; ultimately diluting and cooling.

Experiments done at Argonne labs back a few years ago also suggested that the Uranium will form a cooler coating, as an outer shell. The core may remain molten, but the shell is cool enough to harden, and contain the molten core. The core may burn through the shell, but much of the mass will be left behind, as the molten part runs down into the burned-out cavity below, and the process repeats.

In any case, either of these scenarios would generate significant ongoing outgassing, and none of that has been observed at Fukushima; so it's likely the fuel melted and diffused and cooled. Just like Chernobyl.

Article TLDR version: a cluster of microcontrollers (raspberry pis) does not a real-time operating system (RTOS) make.

The article has to do with deadline-based process timing in a dispersed computing cluster. It has nothing at all do with "network time" which means keeping clocks in sync.