It is best to set your expectations extremely low for this type of acquisition. My personal opinion: Broadcom is _buying_ its way into the Enterprise technology space by hook or crook. When Broadcom acquires a company their M.O. is to immediately install finance-driven leadership and focus strictly on cost cutting measures coupled with accelerated profit-making endeavors. The only thing VMware employees have to look forward to in the near future are layoffs, all types of cost reductions, team consolidations (i.e. you do more work with less resources) and severely reduced R&D. And the only thing that VMware customers have to look forward to are increased VMware costs, more vendor lock-in, reduced satisfaction with support, and almost zero innovation.
Again, this is just my opinion so I could end up be wrong. Or maybe I am just in a bad mood today... meh
One thing that I always gave Dell/EMC credit for was that they at least outwardly seemed to have left VMware free to their own thing. As opposed to a lot of their other acquisitions that they bastardized in this rush to sell enterprises on everything private cloud. We'll see Broadcom ends up taking the same route.
it could be that this is public research vs private?
It's quite exciting to see this scientific discovery having such widespread use, don't you agree? The research is around the [NKG7 protein][1], not sure what Moderna targets.
Sure the more therapeutics use modern platforms, the better it is for humanity, I just wish these articles were written more similar to how a human would want me to understand the differences between approaches instead of trying to make a PR article.
It's a bug deal that they found out about the importance of the NKG7 gene, but the whole article doesn't have a reference to it.
Moderna's personal vaccine is different, as it sequences the cancer itself as far as I know.
Ever tried installing it? It's an incredibly complex piece of work with boatloads of services to configure and debug... and upgrade.
At the time I last tried it (some two or three years ago):
- most of the documentation was written assuming an rpm-based distro and not Ubuntu or Debian (I remember especially having had trouble with subtle differences in iptables/nftables between the distributions)
- on top of that it was right in the middle of a python2 => 3 migration with the result of shit breaking left and right
- it was/still is written in Python which means a second or more for every CLI command to initialize, much less actually do something
- half the instructions in the documentation seem to never have been actually tested, which combined with the two points above made for a really punishing "experience", especially with more rarely-used features such as k8s-in-openstack
- the documentation itself still is (just looked it up) badly organized, with you needing to read four guides (Install, User, Configuration, Ops/Administration) per OpenStack component. Ideally, there should only be one guide for Installation/Upgrade (including Configuration and everything from Ops/Admin) that has everything in it to get all supported parts of the component up and running, one User's Guide that shows how the component is used and what the best practices are, and one Troubleshooting guide.
If you can set it up into a working configuration, it's a nice project for sure. But the road to that point is rough, and you will likely not even want to think about an upgrade simply because of how complex it is.
It's basically consultingware for IBM/Redhat. It tries to be everything you could ever possibly need, the interactions between the components are brittle, and it has all the complexity of a huge k8s deployment except your ability to affect what's going on underneath is like trying to control an angry beehive with a 20 ft pole.
Think Urbit but for sysadmins and you pretty much get the vibe.
Oh, I am glad you liked my blog! Thank you for your sweet words. I hope someday I meet all of my friends from the West bank and maybe share a photo together :)
It's probably a mix of both. Surprisingly (to me), not many were able to break the sub 4min mile immediately after Bannister broke that record - Landy was the second to break the mark a month or so after but he was already working towards it. I read in the 20 year span after the record, only 300 runners were able to match the sub 4 feat.
I've heard a very similar story but with a photo class at UF from James Clear's Atomic Habits. Still, very interesting outcome, although I can't say I was surprised based on the odds. Thanks for the share.
