Most of the software updates you see are a result of CI/CD processes. The industry claims it makes good design patterns to get features our faster and more reliably. In reality it is just a rushed shitstorm that results in half-assed Friday releases that aren't fixed until the following week.
I've long turned off auto update of my apps. Too many times I'm on a trip or other scenario where my tool is meant to be a tool and not some tech bro's rented wet dream, and the tool is broken.
But here's the kicker. CI/CD exists for another reasons or so:
- Frequent updates tend to reset review rankings in app stores. Not only does it offer plausible deniability to the app company, but it also screws with the review scores in their favor, as well as other rankings.
- Great way to help nudge along planned obsolescence. All that pointless rewriting of flash storage on a daily basis.
- Psychological manipulation, it gets notifications in your face to try and increase app engagement, which ensures it is fresh and running gathering user telemetry to sell as a side-hustle, as well as direct-interaction telemetry and getting more ads in your face.
It'd be better if we all just went back to landline phones some days. Modern tech is too noisy, abusive, and intrusive.
Similar history including gentoo and distcc to speed up openoffice and x11 compiles with a pile of old computers.
Put linux on a PC laptop and it just so happens the NVMe controller in conjunction with the kernel driver has some glitch that causes the hard drive to fall off the bus forever. No big deal...
It's great seeing a bunch of
nvme nvme0: I/O (number) (I/O Cmd) QID 10 timeout, aborting
thenreset controller
thenremoving after probe
annnd data loss. Didn't have the patience to figure out the bug in the driver right now. Maybe someday.