I vehemently disagree with this idea. I think you need to understand that all humans are fallible and you should have less vertical power structures and more horizontal structures. Putting all the power into one person's hands is asking for tyrants

There's the theory and there's the real world

Enterprises do that if they choose. Patients can choose as well. And it's their choice, not anyone else's

The laws are, the policing is not. At least not in medical data

I think we were on the same track. I absolutely loved the Amiga and was about to jump on board BeOS when it went under. I never got to use BeOS as a daily driver (just ran their demo disk). How did you find it?

From them internets after the x86 version got out, I think. Played enough with what I found around, and I ultimately bought (with real money) the BeOS 5.0 Personal Edition, made it dual-boot my Linux machine and knew that this is it! It felt like an Amiga but on soulless PC hardware instead! The exhilaration was unlimited! It booted fast, no old cruft, unorthodox designs, everything one-in-a-thousand a true harbinger customer loves!

Eventually I think the setup gradually bit rot with no updates and unsupported hardware, so I reluctantly had to go back to Linux. I remember Ubuntu and Gnome 2 started to look pretty nice (well, for an inferior desktop environment) in the early years of 2000.

(Unsurprisingly, years later Gnome came out with Gnome 3 and killed all the good stuff that Gnome 2 had accumulated. I can only wait and see how long Mate desktop survives.)

I still keep a Haiku VM around and boot it every now and then.

I ran BeOS on both the dual PowerPC desktop and later on an x86 laptop. Thanks to its posix-ish environment, I was able to do all my upper division CS projects on it.

Others who had windows or macs had to "telnet" into a remote Unix workstation in an engineering lab to do the same.

I ran it in a dual boot with linux install but I ended up using Linux more despite liking beos because of the ecosystem. There were just more software available on Linux, especially lightweight tui tools.

No-one ever claimed that Java didn't use a lot of memory. The "comments about Java's GC" used to be about pauses, mainly. Java programmers don't claim that the JVM is conservative with memory use. That said, 5-20x.... nah. Maybe for a toy 'hello world' sized program, but not in real usage

Go's GC is orders of magnitude behind Java's.

I code Go at work. I've been using it for just over 3 years. I really like it. I prefer Java, but Go is a much more ergonomic C and its a very pragmatic language. Except for the *%!@ error system, that can burn in hell.

This was exactly my experience when I first read about Go. I was so excited until I found they were repeating the c experience of check every bloody return value separately. That was the worst feature of c - why copy it

Python's great until you have to refactor a large code base