For the "many eyes" to work, there are quite few requirement.

Yes, being opensource is a requirement, but is not the single only requirement.

The code need to be actually readable and to attract users motivated to check it.
That wasn't the case. OpenSSL's code is known to be really crappy, with lots of bad decisions inside. Any coder trying to review it will have their eyes starting to bleed.
It doesn't attract people who might review it. It only attracts the kind of people who just want to quickly hack a new feature and slap it on the top, without having a look at what's running underneath.

The code need also to be reasonably accessible to code review tools.
Lots of reviewers don't painfully check every single last line of code by hand. Some use tools to do controls. OpenSSL has had such a series of bad decision in the past, that the resulting piece of neightmare is resistant to some types of analysis.

The problem is that some of the design decision behind openssl are so aweful that some of the code review tools just don't work well to detect bug.

Hearthbleed has specifically resisted to valgrind, because the geniuses behind openssl had implemented they own memory management replacement functions in a way that is resistant to memory analysis.
The memory porblem went undetected.

Unintended Affordances
(or why I believe encrypting everything is a bad idea) is worth a read on this.

I am not sure I agree on every point, but it's well thought out post.

With the law in place, including it in the TOS would be superfluous.

Much survived because of monks, but if my history is right (and it's probably not) the enlightenment came from knowledge that survived via the Arabs. Hence we have names like Algebra (from Al-Jabr), for example.

I am seem to recall that during the dark ages the Romans/Italians had around 2-5% literacy rate. Not much knowledge survived there.

There was progression by monks during the middle ages, notably time-keeping and eyeglasses. But I am not sure how much historical knowledge was retained by them. It might be lots - but I've just not seen any historical books to that effect (though I would enjoy reading knowing more).

Small correction: apparently you still call it "pre-embryo" even later than that, as long as they aren't implanted into an uterus yet (and they haven't formed a primitive streak. I didn't remember at all this latter part).

Wikipedia is your friend.

Basically:
- Bunch of cells, still disorganised (apparently, you wait until for the primitive streak to call it proper "embryo". I didn't remember that from my lectures)
- They float around, they haven't implanted into an uterus yet. (That I vaguely remember from my medical studies).

(Well, of course, they were fertilized *in vitro*. It would be hard to find an uterus to implant onto at the bottom of a test tube).

The problem is that there are NO children yet. Only cells with 2 half nuclei inside (= pre-embryos)

The problems are very real, but concerns children which do not exist yet, but due to biology and the existence of those cells could very well come into existence.

The notion is different.
- the "abortion" case is about the mother. It's her body, she decides what she's doing, nobody can force her to undergo a procedure that might has consequences on her health / ability to proceates further.
- here the cells are in a test tube somewhere in a fidgde. mother's phyiscal body isn't in any way concern by the discarding of the cells. it's only the mother's role as a potiential parent (if the children come into existence).

I would venture that this was the VFX family of helmet (VFX-1, VFX-3D)
It was one of the first 3D helmet, with extensive support in games.
Resolution was shitty (~260 vertical column per eye) in fact so shitty, that manufacturer did give separate count of R, G and B pixels (call it "790" horizontal resolution !).
Field of view was also awfully small (think looking into a small windows in front of you, as if you looked a laptop screen, instead of today's occulus rift's "surrounded by the picture everywhere").
Image was blurry (LCD. All this was happening long before the advent of OLED and other fast refresh devices).

But still, even if it was in its infancy, it was one of the first big thing to arrive on mainstream market.
I've never had one my self, luckily the local computer shop had one and I hacked around a bit.

A bit later, the "I-glasses" family of device started to get popular. Much lighter, slighty higher resolution, and used a mirror system that made possible to overlay picture over the actual sight ("augmented" reality).

Personnally, much later, I managed to land an eMagine 3D Visor (was working in medical research, had more money than when I was a kid).
Slightly better angle of view (45 one of the best pre-occulus), OLED display (so no blur, high resolution, etc.)
(though support for non-nVidia hardware required ordering a new firmware on a swappable ROM chip)

Nowadday Occulus Rift and the like have advanced a lot:
- replaced the complex optics and simple display, with simple optics and shaders to compensate distortion.
- actual real full field of view. you don't look through a small windows, you actually have a picture completely surrounding you.
- high resolution (thanks to all the "Apple Retina" and "Cram a FullHD 1080p resolution on a smartwarch" craze, we have small high resolution displays)
- really fast / low latency tracking (thanks to cheap high speed cameras, which supplements the electronic accelerometer/gyroscopes of old time)

We've reached the point where the technical short-comings are more or less being solved.

Thus we aren't as much in the Pong-era, as in the late 8bits / early 16bits console era:
technical problems are being solved, hardware gets available and affordable, now we need to learn to harness the medium and develop nice stuff.
Artists need to learn what can be done with this.
We are at the dawn of tons of new things coming out for VR 3D.

It's good that indie dev are currently thriving.

And I knew it was a good idea to go for AVM's Fritz!Box-es...

(regular updates even for old models, no market segmentation where models only differ by firmware, trying to cram as much feature in one model as possible instead of launching 20 subtly different models, etc.)

So far you've been wrong about just about everything. I know you think that prefacing nonsense with insults makes it an argument but it isn't.

Mainframes do precisely what you claim cannot be done and have done since long before Unix. So your categorical assertions of what can and can't be done are simply and obviously provably false. The fact that rather than admit this and engage you continue to be rude proves that you lack character as well as knowledge.

How can a service handle a situation when it is down? The services have to register in advance how to handle things. Moreover other services might still have issues.

  B depends on C and C needs to reinitiate with B, but D is also talking to C. How does the new B signal C?

As for it being contrived that's one of the key issues in process management how to handle chains and stacks of processes. That doesn't happen much in the sysv world because sysv handles it so badly that everything ended up having to write its own process manager.

Mixed with the sarcasm and the editorial I'm having a tough time extracting the position you are advocating. Or more importantly what you are disagreeing with. The point above is that you can't sue patent examiners. Your position seems to be that patents should be subject to a more complex and hostile review (i.e. a much more expensive review). If that's your point I'd agree. Otherwise you are going to have to represent.

Supercomputing? HAH!Linux is so fucking weak that it can't even support my super-server with 12 GPUs PER BOX.

http://www.top500.org/statisti...

In 2011 Cray deployed a Linux supercomputer with 9600 GPUs and from that point on Linux has been able to handle essentially infinitely many. I think you may want to read up a bit.

RedHat has had their own kernel for a quarter century. They don't need Linus' permission to introduce change into their kernel.