Either that or it's a persistent urban legend.

Garbage regulations like IP create these behemoths. If you want freedom, stop regulating monopolies into existence.

Is that true? I can't find any reference to it, and it seems like the kind of thing that would be documented, if only to make fun of it.

Statism creates billionaires.

And because they knew the product was going to die anyway. Open source alternatives have caught up and there's nothing to keep customers from switching.

This isn't a justification, but it's an explanation. If they thought VMWare would be a long-term cash cow, they would keep it going. They know that won't happen, so they've opted to squeeze as much cash from it as possible, as quickly as possible. They recognize that will accelerate its demise, but apparently believe it will make them more money, since they won't have to invest anything in maintaining or marketing it.

I'm surprised they aren't more worried about legal action, though. It seems like it would be safer to continue complying with the contracts, perhaps with far inferior (and far cheaper) support quality until those ended. As for the perpetual licenses, it would seem safest to just shrug and say "Yeah, you can keep using it, and we'll keep giving you every update we release", while cutting the engineering team down to nothing. The aggressive approach they're taking seems likely to net them some ugly fines after some uglier legal fees.

Not remotely. US hospitals are required by federal law to provide emergency care, regardless of ability to pay.

It's absolutely not even the thousandth time a researcher has submitted an invalid report, then whined about not getting paid for it.

This is correct. Mod parent up.

But it's not a vuln. So it would be worth nothing.

For a report that isn't a vulnerability? Well, it would have cost them $50k, and they'd have gotten nothing for that money -- other than to encourage researchers to submit invalid reports.

Also, a bunch of Google Apps. Moto bundles those as well. You apparently don't consider them crapware, but other people disagree.

As for Facebook, etc, there's another class of "virtually pre-installed" apps (I forget what the actual term is) which aren't actually part of the system image. Instead, the system image has a list of apps the device will automatically download and install after factory reset, so they're present by default but you actually can remove them. Whether Facebook is really pre-installed, virtually pre-installed or not pre-installed depends, of course, on the OEM and how much Facebook is paying them.

Google's terms mandate, of course, that even pre-installed apps can be disabled. OEMs are not allowed to block that.

Not being much of a gamer I haven't followed this story (at all!) so the headline and initiative name "Stop Killing Games" made me think it was 1.3 million signatures from people who want to ban games in which people are killed. "No way that's going to pass," I thought. People love virtual murder.

Then I figured out that it's the killing of the games people want to stop, not the games that include killing.

Vaguely related, I had a serious EverQuest addiction ~20 years ago (the reason I gave up on any but the most casual of gaming), and I noticed a few weeks back that it's still available on Steam, and free to play, so I downloaded it and logged on, and even found my old character still there (though with zero gear because I gave it all away when I quit playing). The UI is dramatically different, but the general content seems the same. It's no longer very interesting to me, though.

The pre-installed apps are just as unremovable on Moto as any other (unless you unlock the bootloader; some Motos have unlockable bootloaders). It may be that you define their pre-installed apps as not crapware, but that's a judgement call, not a statement of technical fact.

Yes, that was the joke. Maybe too much of an inside joke, but isn't this supposed to be a nerd forum?

Disable, yes. Uninstall, no. If it's pre-installed it's part of the system image, which is mounted read-only and protected with fs-crypt. Actually modifying that would require root access to remount it rw and to disable fs-crypt.

That would also, of course, completely destroy the Android security architecture, leaving you wide open to all sorts of attacks. If you want to do that, get an Android device that has an unlockable bootloader (e.g. Google Pixel), unlock it, then do whatever you like. And be sure not to hire any evil maids.