Live data from Hacker News

Broadcom to acquire VMware for $61B

reuters.com

401–410 of 430 posts

Re: Broadcom to acquire VMware for $61B

#401

Earlier quoted context omitted.

The key is in "derived from". Very few people would say NT is derived from some random drivers that nobody at Microsoft had a hand in writing. Taking existing code and having it form the foundation of a new kernel and claiming it as all closed source is quite a bit more obviously derived from that existing code open source code. "Derived from" is the core concept in the GPL; it actually doesn't use the word "link" at…

I thought they ripped the network stack from BSD. https://www.neowin.net/forum/topic/381190-windows-tcpip-stac...

That's fair, I should have kept constrainig my statements to GPLed code. That being said, Microsoft complied with all of the license terms of that stack (basically shipping a copyright notice and constraining themselves on how they advertise it's use). If it was a GPLed stack and they never published source, I'd be saying the same thing about them that I'm saying now about VMware.

Re: Broadcom to acquire VMware for $61B

#402
post #312

Earlier quoted context omitted.

I was very surprised when the product quality went up, for the Symantec software I use.

To be fair, prior to broadcom purchase symantec was not known fo high product quality In the sysadmin world, Backup Exec and Norton products are meme's at this point, examples of the worst kind of software so I am not sure how it could have gone down in quality

The consumer grade Symantec software and enterprise Symantec software were always different.

Norton never had any real bearing on SEP.

The consumer side of Symantec was not sold to Broadcom and became Norton Lifelock.

Re: Broadcom to acquire VMware for $61B

#403
post #307

Earlier quoted context omitted.

Fascinating … your very comprehensive list does not contain the only VMware products I have ever cared about: workstation and fusion.

And has a lot of "similar to {thing I have actually heard of}"

It reminds me of the first episode of Saturday Night Live after the original 1975 cast all left. In the first episode, the new cast did a sketch in which they each described themselves as a version/variant of/similar to a member of the old cast.

(Everyone was fired after that season, except for Eddie Murphy and Joe Piscopo.)

Re: Broadcom to acquire VMware for $61B

#404

Earlier quoted context omitted.

You can run Windows in Docker. Ether figure it out now, or in 2 years when VMware starts to suck. Then again, all the big companies I know put things off until the last moment. If I was a better developer I'd be putting together a project right now that allows you to run all your happy legacy Windows software with Docker. Shouldn't be hard to raise a bit of funding for such a project assuming you have the right backg…

> You can run Windows in Docker ... on Windows. So it doesn't really mesh with a typical server environment.

Ok, use Windows Server as your host.

Or use Virtual Box on Ubuntu

Re: Broadcom to acquire VMware for $61B

#405
post #340
post #260

Earlier quoted context omitted.

They also offer tanzu as on prem cluster where you can somehow use kubernetes to provision kubernetes virtualised kubernetes clusters.

It uses cluster-api to provision clusters. It's very cool and isn't a VMware thing. It's open source, and you can easily run it on regular k8s clusters. https://cluster-api.sigs.k8s.io/

Yes it is a community project but VMware engineers play a big part in maintaining as it is foundational to the kubernetes product that VMware sells. Open source does not mean it runs by itself.

Re: Broadcom to acquire VMware for $61B

#407

Earlier quoted context omitted.

How do you propose banning this while permitting open source drivers for Windows? I understand why you might want to, I just don’t understand what the rule would be.

The key is in "derived from". Very few people would say NT is derived from some random drivers that nobody at Microsoft had a hand in writing. Taking existing code and having it form the foundation of a new kernel and claiming it as all closed source is quite a bit more obviously derived from that existing code open source code. "Derived from" is the core concept in the GPL; it actually doesn't use the word "link" at…

They did publish the source to the GPL drivers as well as to the vmklinux “adapter”, and I don’t believe either the core hypervisor or the ESX kernel were derived from or adapted from the Linux kernel.

My impression is mostly people are annoyed that VMware drafted off the Linux driver ecosystem and used it to help bootstrap a proprietary ecosystem.

Eventually (once they were successful) they published a native driver SDK and hardware vendors wrote native drivers for it.

To me this seems very similar to the way Linux had for a while a way to run Wifi drivers originally written for NT, though it didn’t lead to the year of the Linux desktop as some of us might have hoped for at the time.

Re: Broadcom to acquire VMware for $61B

#408
post #367
post #353

Earlier quoted context omitted.

I have customers running Tanzu. It is slick, but niche. Incredibly rock solid - in ways K8S is not - and you pay for it. It is on its way out as a product.

Tanzu is a loaded term :) Are you talking about TAS (ex PCF) or TKG?

PCF

Re: Broadcom to acquire VMware for $61B

#409
post #353

Earlier quoted context omitted.

I have customers running Tanzu. It is slick, but niche. Incredibly rock solid - in ways K8S is not - and you pay for it. It is on its way out as a product.

Why is it on its way out as a product? Is it simply not making money?

The scuttlebutt I hear is Kubernetes is stealing its lunch money.

Again, referring to what used to be PCF. Hence why the more modern Tanzu is K8s based.

Re: Broadcom to acquire VMware for $61B

#410
post #298

Earlier quoted context omitted.

Given the situation of Docker, it doesn’t look good for the monetization of Kubernetes, or am I missing something (I‘m not too familiar with Kubernetes)?

There's stuff like Openshift and Rancher as commercial Kubernetes distributions as well as a lot of Kubernetes "addons" like weave, portworx, etc. Monetisation of Kubernetes is totally possible. Docker failed because they tried to compete with Kubernetes, lost and then didn't have a clue how to find a niche where they could enrich the Kubernetes ecosystem.

If you're looking for an example of successful monetization of open source addons for K8s, you could do much better than the example of Weave Net.
Post reply on HN