Minor version bumps should be mostly trivial: Change version and hash, package that into commit+PR (ckeck guidelines on that!) and that’s it most of the time.
The harder part is QA; ensuring it still works as expected. Therefore, even just testing update PRs as they come in would be a great help.
If the code change is trivial and a user of the package said it still works for them, a commiter coming along is likely convinced of the PR’s quality and just merges it.
It’s super easy to contribute to Nixpkgs in a meaningful manner :)
Original price doesn’t matter, you need to compare it against current new offerings. A drive like that, I’d buy for 8-10€/TB at max. because current new HDD pricing is 15€/TB at the low end.
What you also need is SMART output. Watch out for high uncorrectable errors, writes and whatever. I’d never buy a drive without having seen its SMART data.
It used to use Google search results but they switched to Bing. It is worse than Google.
That’d be news to me and an ad hoc comparison I just did shows results much closer to Google than Bing with results usually just locally having switched places while on Bing it’s an entirely different order.
They do(did?) use Bing for mobile search results because daddy Google forced them to not be competitive on the platform they’re most interested in.
I homebrew the ROM on my personal phone and I can tell you from first hand experience that you need the vendor dirs extracted from the OEM ROM. You can read up on that on the wiki pages for building any device ROM.
You can also come to that conclusion the other way around: How else would you (or LOS maintainers) get your hands on proprietary blobs full of secret sauce that vendors sometimes even try to actively block access to?
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.