Only tangentially related, but if you ever get the chance to check out the Patek Philippe Museum in Geneva you should do so. I'm not really a watch geek so before going there I was kind of "meh", but that place is incredible.
They have thousands of timepieces, some dating back to 1530. To see what people have been able to accomplish with nothing but springs and tiny gears is nothing short of mind-blowing. As a technologist it's pretty humbling, considering all the advantages we have today and yet ancient watchmakers could do this work literally with nothing but hand tools.
I/O isn't an object, it's an interface (Go has no objects). There is nothing magical about I/O or any interface--they are just functions--so this change would require extra magic to be implemented which I strongly oppose.
One of the beautiful things about Go is the designers carefully chose to confine language magic to only a few fundamental areas (channels, goroutines, arguably maps) and resisted going beyond that. Go approximates "C plus Concurrency and Better Data Structures" and nothing more.
Vault is a nice piece of engineering (we use it), but it has what I call serious "backend-itis". Everything is pluggable, which makes it a bit of a nightmare to understand and use. For example, "secret backends" and "storage backends" are entirely separate things, but the docs aren't super clear about it (not to mention auth backends, audit backends, listeners ...).
Unsurprisingly it buys completely into the Hashicorp ecosystem (Consul, weirdo HCL configs, etc) which is a plus or minus depending upon your perspective I guess. Vault servers are also stateful, which complicates deployment (you can't just stick N Vault servers behind a load balancer).
If I had infinite time I'd consider creating a "SimpleVault" fork consisting of exactly one secret and storage backend, one way to auth, one curated workflow and make it run in a stateless manner. I'd probably also remove all the clever secret generation stuff, since 90% of applications just require a secure place to store secret blobs of data, as opposed to creating dynamic time-limited IAM credentials on the fly or whatever.
Reading a little deeper into the article, they actually are prohibited from distributing any assets to private persons (shareholders, physicians). Yet even the CEO claimed otherwise at one point.
As a nonprofit they should have taken their surpluses and used them to offer low cost health plans or other social benefits. Instead they just hoarded the cash.
Prolog is really interesting. There's also https://github.com/mcsoto/cosmos which transpiles to Prolog, I believe. It looks like the latter isn't actively worked on, unfortunately.
When Ruby or Python is too slow you can switch to something else. When JavaScript is too slow you have to either pay someone to make your code faster or pay someone to make the browser faster.
Here's a big, dark secret: being a physician isn't really that hard. Sure, there's a lot to learn. Yes there are some physical techniques that must be mastered (lots if you want to become a surgeon). But the raw intellect required is not especially high--anybody above the 66th percentile would likely do just fine.
A long time ago I was in pre-med. Similar to the article, I got a 35 on my MCAT. I know a lot of physicians. They're all very smart (because you have to be to get into medical school). The vast majority of them are bored with medicine. They do anything they can other than see patients. Some invest in real estate, some manage other physicians in a group practice--there's one guy who built a small datacenter and runs a business selling electronic medical records systems as a service to other medical practices!
The point is--the practice of medicine kind of sucks. It's mostly the same things over and over, with a lot of paperwork thrown in. Med school lures in the young with the prestige attached to the magic letters "M.D." and because med school is an ultra-exclusive club for smart people. The sick joke is that after all the work and sacrifice and expense the job usually isn't worth it. If you want to be a doctor, imagine yourself working in subsaharan Africa helping the neediest, poorest people imaginable. If it doesn't sound like something you'd want to do, you don't like medicine enough for the career path to be worthwhile to you.
They have thousands of timepieces, some dating back to 1530. To see what people have been able to accomplish with nothing but springs and tiny gears is nothing short of mind-blowing. As a technologist it's pretty humbling, considering all the advantages we have today and yet ancient watchmakers could do this work literally with nothing but hand tools.