Odd, because with TLP I can actually reduce battery wear by setting limits. I don't know how that makes OEM decisions complicated? They chose to not support Linux. Other companies like Framework and Lenovo implement Linux support through some select models and offer to install Ubuntu or Fedora. I understand having a zero software warranty for Linux, but no firmware/EC support? I remember owning a shitty (as in HP) HP Envy x360 laptop (RIP) that couldn't even wake up from ACPI sleep on whatever kernel Mint was using at the time. I think it was at the time I heard a rumor they just weren't implementing ACPI (open standard) properly.
The point about a single dev taking out multiple programs isn't exactly wrong (relevant xkcd). But it's a very entitled attitude. If part of the stack is that critical to you (especially for business), maybe consider supporting it or contributing to it.
The real issue is knowing when this is the case. Has anyone seen a solution for that?
a single dev taking out multiple programs isn’t exactly wrong
It's also not unique to F/OSS. This could well happen in a business, and often does.
Has anyone seen a solution for that?
Short answer, anything that does dependency tracking and pinning. If a new release of a library comes out, you shouldn't just upgrade to it without testing.
On a desktop Linux OS, I would expect the distro maintainers to do that testing before it gets pushed to their repos (as an example).
Madthumbs - the account named after a defunct porn site, creates a “Linux sucks” community (from which I was banned on day 1 lol) to spread lies about shit that’s already solved, or things that are a problem for any OS/computer hardware as an exclusively Linux problem and anyone takes that shit seriously?