Disclosure: I happened to speak to one of the former VMware Fusion product managers about this, but I have no affiliation with VMware right now.<p>This is technically true. The issue was that VMware Fusion was lagging because of political / budget / turf issues.<p>This could also actually be a move to get new blood and breathe new life into a fairly stagnant / de-facto abandoned product, which a lot of people depend upon for hypervisor-oriented local development, demos and many other enterprise use-cases that aren't always obvious.<p>I use VMware Fusion almost everyday, it's stable enough and it does what I need (nested virtualization) and no more. It's fine, I hope it keeps up but doesn't get crappier... It's unclear whether any "new" dev team can avoid teething pains, unplanned breakages or becomes too retail spammy as other solid but maintenance-mode apps have a habit of falling into.