1.) VMware had (and still has) a lot of goodies on vSphere that were (and some still) are not on competing products. If your Virtualization strategy depended on any of these, migrating is hard.

2.) Take point #1 and multiply by 20x if you have (private/public/hybrid) cloud foundation.

3.) If you were a single-virtualization or single-(private)cloud vendor based shop, you probably want to migrate to a multivendor stack as part of THIS migration, so that, if one of your new vendors goes rogue (just like VMware/broadcom did) you are not trapped again. This complicates even more the migrations, as, you will need to handle a multivendor environmet, and more so, for a while you will have to juggle 3 vendors (WMware + the other 2)

4.) For ages VMware was a model citizen, which means everyone certified agaist them. Before the migration you need to make sure all your workloads are certified. This is 4x valid for purposes of regulation, certification, compliance, and (cyber) insurance

Is a very complex issue, for many an organization is not as simple as "I migrated the VMs in my homelab in an afternon so how hard can it be?". And the timelines are heavily compressed.

And tell me it does not sond like Meta Muse AI

Then, there is an AI specialized on Law, is called Harvey, Like Harvey Dent the district attorney - Two face, from Batman

Who is naming these things?

Considering I use MacOS 15.8, bootcamp into Windows 10 for gaming, and nowadays my only linuxes are on my NAS (DSM 7.3) and 2 VMs, one with TAILS and one with Kali, I am not worried in the slightest about what happens with Canonical...

about the volume of work, they should be using LTS or SLTS kernels, instead of bespoke Kernels. For instance, Ubuntu 26.04 LTS uses kernel 7.0 (not LTS, and certainly not SLTS), which means canonical engineers have to do all the backporting and patching work...

Anywho. Good luck to canonical and their users.

I used F-droid on my Blackberry Q10, and KeyOne, But I used so few apps from there, and all of them were on the official playstore, so, at the end, for my Razr+ 2024, I did not bother to install F-droid.

Still, glad to see the team moving forward, I desire them good luck, and have nothing but gratitude towards them.

Is all the other bibs and bobs that hang of the chip. Mem controller, GPU, NPU, USB controller, networking, wireless, the works

Since I live In Venezuela, Qualcomm does not want me to read the blog post.
So, I have a question for those who have read it, as TFS does not say:

The Qualcomm integration work is fully FOSS drivers? Or is a bunch of closed source drivers and binary BLOBs.

I do not care one way or the other, as I am more pragmatic than ideological in that regard. But I do know that with Closed source Linux drivers:
1.) In the tail end of the life of the hardware, support becomes spotty, as newer kernels stop supporting the closed drivers.
2.) Oftentimes the reverse engineered FOSS drivers lack certain features and lag in performance the closed source counterparts (nVIDIA drivers, and old AMD* drivers come to mind as prime examples).
3.) Certain important projects ARE ideologically minded and flat out reject any closed source drivers and BLOBs, so that restricts the projects one can approach (of the top of my head OpenWRT, but that is not relevant to Snapdragon X2).

I hope Qualcomm becomes "good Linux Citizens" and go "full FOSS drivers and firmware" like Intel and AMD, but I wanted to make sure.

* One example dear to my heart, FOSS AMD drivers for the Xpress200 chipset in modern kernels lack support for the s-video out, that propiertary drivers have. And an old kernel/distro will not do, as the use case was connecting a latop to the net so that an old CRT TV could display youtube and other net content. Don't ask

And yet "Crab People" is one of the few things to which "Simpsons already did it" does not apply

Crab People!
Everybody panic!!!!!

https://www.youtube.com/watch?...

Simpsons already did it.

Given the pitance we pay in Venezuela for the tickets (something like U$D 6 for 2 tickets), this wil barely register in the "profitability" part, but, at least, is two more butts on seats for the stats.

Could have seen it in streaming later on (is not like this needs a big screen, or has some art-sy quality), but I wanted to show support in the only way I could.

is that 6 months out of the year you can operate the datacenter without Aircon.

Imagine the energy savings.

Oh, wait, is even worse, because LTS and SLTS kernels will receive AI patches. You will have to fork the last Non-AI kernel, and develop all the patches yourself, without ever again looking at the Linux mainline code, as some of that may have AI patches in it... Also, if you want that kernel to suuport new hardware, you will have to write the changes yourself...

Good luck with that.

Tell us how that works for your favourite "non-AI" distro in 2040, when the last non-AI SLTS Kernel (6.12) has been going without any patches for 4 years.