There will be no next. Broadcom will get blood from the stone, rest assured. They will continue to raise maintenance and licensing fees until they very last customer turns off their last ESXi box. If you think IBM and mainframe is bad, you've never lived with a technology that Broadcom has acquired.
And don't get me started on trying to get their chipsets working on Linux. Up until recently, it was nearly as bad as nvidia's garbage. Even now, I'm not sure if everything is well supported; I've avoided BRCM wifi like the plague for years now.
Cheap is nice, but I miss the days when chips did things you wanted.
Before that Broadcom was (and still is) one of the larger communication hardware companies, making chips for cell, wifi, bluetooth, ethernet and ARM SoCs, along with telecom and data center boxes that used these chips. You almost certainly have their hardware in some device you own. But they have always had difficulty competing with Qualcomm, arguably in part due to anticompetitive behavior from the later.
After the acquisition, they have been acquiring enterprise software companies to diversify, including CA Technologies (think Atlassian/Oracle of the mainframe world), Symantec, and now VMWare.
Given that CA already had the reputation of "where software goes to die", this is ... bad news for VMWare. (I'd heard that description from many in the tech field, including from a CEO who's previous venture had been acquired by CA.)
I also hadn't realised that Broadcom itself had originated at HP.
The company that would later become Broadcom Inc. was established in 1961 as HP Associates, a semiconductor products division of Hewlett-Packard.[12]
The division separated from Hewlett-Packard as part of the Agilent Technologies spinoff in 1999.[8][13]
<https://en.wikipedia.org/wiki/Broadcom>
Citing: <https://books.google.com/books?id=WAW5DwAAQBAJ&q=1961+broadc...>
Part of me thinks that corporate acquisitions and mergers should not be permitted to use prior names, and especially not to adopt the name of an earlier, non-ancestor parent.
See AT&T and Lufthansa for a couple of examples.
Its history goes back to the 1960's. It is a major semiconductor company that I would say, was part of the ecosystem that made computers and networks possible.
You haven't heard of them because they make too much of everything that makes the fabric of everyday computing.
It's like how you would never really know of the company who made the pipes for your toilet/plumbing.
And more recently the working progress which is Intuit's acquisition of MailChimp.
Yeah. They have done a better-than-most job of trying to default to open (for all of their other failings)
As for helping divide society/ politics, have you paid attention to HN front page the last few days? Wave and wave of OpenAI posts, with huge amount of ignorant, uninformed, speculative, conspiracy driven, repetitive, divisive comments that got endlessly upvoted and promoted. That reflects who the HN audience is and what we are interested in. You may say that HN also helps divide society/politics. Yet you, and I, are still here.
I had one friend super into Tekkit but frankly "automate things so you can automate those things better" games never appealed to me a ton.
Take a look at this: https://www.youtube.com/watch?v=rR8W-f9YhYA
As I understand it, web Outlook pioneered numerous browser innovations that we take for granted now.
It's so bad, we have a dedicated email HTML person.
That's such a low bar. I'm still on "classic" at work, and I can't imagine what they would have to do to make it worse.
The programming languages? What's the story there, were they acquired?
I used to work for HPE on their OpenStack team, and getting support, even as an employee, basically required me to have a rolodex full of engineers all over the world. A tremendous amount of troubleshooting was just looking up who had committed code, then tracking them down when something blew up.
hmm, why would people still use VMWare? Honest question. Maybe there are some licensing issues I'm not aware of. Isn't vbox open source? If not, wouldn't even things such as https://copy.sh/v86/ in the browser would do most virtualization trick now days?
The money making part of vmware licensing is the baremetal hypervisor ESXi, the competitors are xen or hyperv and the likes.
The lock-in part of vmware is the vsphere management software, that allows you to move VM's en mass from one baremetal machine to another baremetal machine, or allows you to nest vm's, etc. manage your entire fleet of vm's which could be thousands or hundreds of thousands of virtual machines, from one management interface.
it's basically docker except it's actual entire vm's being moved around. VMWare ESXi being a baremetal hypervisor means you can run different OS's on top of these vm's and imagine being able to move these VM's all running different OS's around in your ecosystem.
That's what people pay the big bucks to vmware for.
It would be very difficult to build the vsphere/esxi ecosystem with pure opensource tools (it's possible with Xen, etc) but you'd be right back at paying some vendor a massive amount of money for building, integrating, and supporting this kind of system. (Redhat will happily sell you something that approximates vmware's tools, for megabucks).
As an aside, the consumer "vmware" software that you install on your workstation is such a small portion of their business, they basically spend no money on fixing/upkeeping. Apple silicon support was in beta for a loooong time, and they don't actually care about their workstation product. ESXi makes the money.
1. vmotion + storage vmotion - you can live migrate a vm from one hypervisor host machine to another. you can also live migrate the underlying storage (good if you want to consolidate storage servers, rebalance disk load, etc). with some caveats, you can do all of this without any downtime in the vm. it's not just a simple suspend on one host, resume on another host. a memory snapshot is migrated while the vm is still running on the first host, and when the amount of dirty pages starts to converge, they flip the vm over to the new host. similar idea for storage vmotion.
2. fault tolerance - for single cpu vms, you can use vmware's record-replay technology to execute a secondary vm in a "shadow" mode which replicates all of the nondeterministic events across the network. if one hypervisor host dies, the other can take over with no downtime. this is great when you need to add HA for a legacy application.
3. vsan - generally you run these systems with some sort of shared storage (nfs or iscsi attached SAN, or something like that). a SAN can be really expensive and a single point of failure. vmware can create a "virtual san" from a cluster of your esxi hypervisor hosts. as you can imagine, it has all sorts of HA features and can rebalance workloads to improve performance.
there are more, but that's just a few interesting features.
But it has been solid otherwise, even with in-place upgrades over many years.
I haven't run proxmox so can not directly compare :)
In every scenario that we spec'd out vSAN for production use it came in at least two times as expensive as your average dual controller, HA capable, storage array.
vSAN pricing is absolute nonsense.
In edge deployments where rack space is tight it's actually a great solution if you only have a few U to work with and have a HA requirement for a legacy app as well.
See VM.pool_migrate and VM.migrate_send https://xapi-project.github.io/xen-api/classes/vm.html. Those features got introduced in Xenserver 4.0 (2007) and 6.1 (2012).
Disclaimer: I work at XenServer.
Actually, no, they apparently won't, because I tried and was told they are discontinuing that product. They are going full steam on their OpenShift (k8s) product though, and will be happy to inform you that you can run a VM on that, but if you press them you'll find that you're actually running a VM in a container, and that you have to specify it as a k8s deployment, so apparently you can't just throw a VM up like you can in vCenter.
For the desktop, VirtualBox isn't much better. At one point after Oracle purchased it, they were tracking your IP and if they found you were using their extension pack that provides essential capabilities like USB 3 support (only the core of VirtualBox is GPL) and it was for commercial use, they were hitting you up for a license [0].
[0] https://www.theregister.com/2019/10/04/oracle_virtualbox_mer...
Think servers with four digits of days of uptime, in terms of things you probably shouldn't do, but absolutely can.
Source: I’ve responded incidents on those guests. It’s terrifying, but hypervisor uptime is limited by power not OS choice.
These days Windows is stable if you don't touch it.
VMware is stable even if one of the disks is out of space, the fibre is flapping, some idiot misconfigured the switches, and the whole cluster has time out of sync... by seven hours.
That's not hyperbole, that's an actual cluster that I got given to look after. It was running like that for months, perfectly fine, with VMware HA just "taking care of things".
If you sneeze in the direction of a Windows Failover Cluster it'll... fail.
Esxi is an enterprise product which engineers are familiar with, the cost of the product vs the cost of migration and upskilling in alternative tech should not be underestimated, particularly when it’s the thing that runs all your other things.
Edit: in case you’re not aware, many organisations still leverage on-prem virtualisation technologies - that might not be obvious to people that haven’t seen it.
Everyone has heard of it, it's theoretically comparable to the likes of VMware/Parallels desktop hypervisors, and it's cheaper. But just like spam (compared to ham), it's also obvious to anyone that's used both that it's by far the worse option, and there's very few reasons to use it besides cost, while there are numerous reasons to use one of the better alternatives.
In general, performance is significantly better with other hypervisors, but in particular shared filesystem performance (ie sharing a directory from the host OS into the guest) and features are lacking on virtualbox.
It's the default provider used by vagrant, and even the vagrant team recommend using a different provider for "any serious work".
Of course one could argue there's an even higher percentage of inedible parts in the canned monstrosity because it's all inedible, and I wouldn't argue that view point is wrong.
Hams like that often go on sale around US Thanksgiving and Christmas, with prices for them around US$4.50-6.50/kg last week and probably as 'loss leaders' around US$2-3/kg the week before Christmas. Ham is a regular part of 'traditional Thanksgiving' but not as much as turkey, whereas the 'Christmas ham' is definitely a thing.
One. NEW. CRITICAL. Alarm.
VMware's revenue for 2022 is $13B, and net income about $1.8B. Trim sales department, remove duplication(HR, IT, etc), cut down development, remove many make-work projects that the middle management engages in, increase licensing/support cost. They will focus more on net income, financing costs for $69B will be taken care of by layoffs and other stuff.
Sure, without a doubt, there are exellent devs to be found worldwide.
But let's face the reality ...
Western corporates don't go outsourcing in India for the talent.
They go outsourcing in India because they want to wield the axe on what they perceive as the expense of Western developers.
So, if they're not willing to pay Western developers, they're not exactly going to be looking at the premium end of the Indian talent pool either are they !
Especially as a typical remuneration structure for senior management is that you are rewarded with a bonus based on the amount of cost-cutting you've achieved.
I beg to differ.
You're either ignorant or have no idea how many SW and HW you interact with regularly from big name companies, has been through the hands of skilled Indian or other offshore devs which while being cheaper than American devs, are in now way worse programmers, sometimes the opposite.
You seem to equate pay only with talent and skill, but that's rarely the case. Lower paid international devs aren't necessarily worse than their American counterparts and well paid American devs aren't always better than international talent.
Your pay is more a function of opportunities and supply/demand in your area rather then purely on your own skills. Otherwise explain me how the same international devs who struggle to crack 50k in their own developing country can suddenly score 200k+ the moment they're in the American labor market. They don't magically become 4x better coders the moment they cross the border.
I am also not disputing that there is a proportion of companies out there who go to India for all the best reasons, a genuine quest for talent.
But sadly, I think we have to accept the reality that such companies are very much in the minority. The reality, sadly, is that the majority of companies who outsource to India only do so for one reason. Aggressive cost-cutting.
Of course companies will optimize for the best bang for the buck labor the same way you optimize for the best bang for the buck products when you shop for something, that's how capitalism works, it's a two way street.
Now if the move to India, or anywhere else, lowers the development cost without lowering the product quality, why is that a problem?
I would understand this being an issue when offshoring causes the quality of the product to go to shit, but it often isn't the case anymore, so what's then problem here?
Unless of course you mean the problem is "THEY TOOK OUR JOBS!" which would be understandable but like I said, capitalism is a two way street.
Supply and demand. American companies needed "developers, developers, developers", and when the supply is very finite and at the same time the investment markets were flush with "dumb money" that begs for at least a pittance of ROI, so in the end they ended up in bidding wars.
So now when a developer from <insert poor country here> enters the US labor market, their market value increases simply because they are now adding to the supply side of the US labor market - them being in the US is the factor.
In India, because of different levels of pay, one can get trained for first few years by working for cheap companies. Once they hone skills, they go for companies that pay them top: companies even below WITCH -> WITCH -> American companies in India -> American companies in America; that's how the pipeline works there. In the states, this pipeline is completely gutted: every company wants rockstars or hires fresh grads from select schools.
Also, you're making it sound like the devs can do whatever they want and happened to deliver cool new features. As said, back then everything hinted at them just switching Workstation to maintenance mode and letting it slowly fade into irrelevance, so it wouldn't have mattered how brilliant that new team was.
I bet the problem is that they are too “enterprise” and couldn’t price it low enough. If it were too expensive it wouldn’t be competitive with big cloud managed offerings.
Really it’s just Hyper-V with extra “cloud management” bits (“Azure Arc” and friends), but it’s _relatively_ friendly to manage alongside your Azure cloud resources once you set it up.
Bottom line is, I really don’t think they’re worried about on-prem hypervisors competing with Azure!
I actually thought that vSphere offers some stuff in the hyperconverged area that Hyper-V doesn't, this is where I could see it competing with Azure. However it seems Hyper-V with Storage Spaces Direct seems to be pretty much on par, at least on paper.
So there's even less reasons why MS would be interested in VMware. Only maybe to get rid of a competitor.
Obviously if you’re running dozens of hosts and thousands of VMs, needing live migration and things like that, then it’d probably be missing a lot of features you’d want, but for smaller stuff it’s pretty crazy how well it works.
I really thought there was a strong play there to do a major private cloud play as part of Dell's 'come back story' and then nothing.
But maybe that's exactly the problem. For a container based solution you still need a hypervisor but if you invite hypervisor people to the table, to they really want to champion linux containers or do they want to try to reach a local maximum by squeezing all of the fat out of VMs.
Even the Java to an extent 'got it' more than Dell+VMWare. I abandoned Java as a platform right around the time Docker went from whispers in dark corners to a quiet ping on people's radars. Within a couple years of that, the JVM team had increased their level of effort to shrink the system footprint from what I would label bet-hedging to aggressively. You need a small JVM if you're going to pack five services and/or ten JVMs onto the same host. Initially J2EE imagined itself to be multitenant, and it did a poor job of re-implementing half of Erlang, poorly. Containers were clearly on their radar.
VMware under EMC $625M acquisition lasted ‘04-‘15
Dell acquires EMC for $58B in ‘15 which includes previously acquired VMware.
Now Dell is trying to balance their books and sells entire stake of VMWare in ‘21.
Broadcom now picks up the pieces of VMware with acquisition completed this year (‘23).
I wonder which corporate overlord will take it over in the next 4-5 years.
Maybe Oracle or MS will be the next to bag hold.