The way it’s written doesn’t say whether it simply isn’t made to work for Firefox or whether it couldn’t be made to work for Firefox. Fortunately, the latter appears to be the case.
Well, you can roll back with a switch too; no reboot required.
The VM protects you from accidental state modification however (i.e. programs enabled by some DE by default writing their config files everwhere) and its ephemeral nature makes a few things easier.
The vendor blobs in custom ROMs come from the stock vendor ROM. When the vendor stops publishing their stock ROM, the custom ROM’s will also stop coming. In some cases some BLOBs can be taken from similar devices that might be supported a bit longer but I believe this is quite rare.
The ROM itself still gets updates through the AOSP but vendor BLOBs stay where they are and open source devs can do little to nothing about that.
For the first year or two, that’s common. Getting feature updates for anything even approaching >5 years is near unthinkable for Android devices however. You only get that with custom ROMs and even there it’s only half of the story as they can’t provide security updates for vendor blobs which is kind of a big yikes.
The iPhone 8 will get cut off the newest feature updates in the upcoming iOS 17; 6 years after launch. Security updates will likely be available for years to come. For comparison, my OnePlus 5 from 2017 (1 year younger) received its last update (any update whatsoever) in 2020 (3 years ago).
With an Android device, you’d be lucky to get security patches in any regularity at all, much less >3 years after release. That only happens with a couple few vendors who actually care such as Nokia and maybe Google (to a degree).
I don’t see how that point is relevant as that claim was never made.
The claim was that Android phones usually barely get updates which maps to my experience. Updates more than one or two years after the release of a device is the exception, not the norm.