This shouldn’t be our responsibility to “fix”.

This is what charge backs are for FYI.

“I’m sorry, but you failed to provide a service. Either give me a full refund or I will start the charge back process with my credit card company and you’ll be forced to explain why your refund policy violates their ToS and any penalties that arise from that process.”

I just wish it was an either/or situation.

I don’t always need my lawn mower/blower/weed trimmer on batteries. I wish I could easily plug them in when doing light dut work close to the house. But then they couldn’t tie me into their battery ecosystem as easily.

Do one of the following:

1. Tell your mother you’re not comfortable hosting that type of content as a non-believer.
2. Lie and hand back the propaganda movies and say you couldn’t rip them to some unknown rip protecting they use and there’s not enough resources online to figure it out.
3. Host the content and let your mother liver her life and don’t say anything.

I’d personally use option 1, but you do you.

Firefox had some major memory leaks when Chrome first launched (2008). It became noticeable with the more tabs you had and the longer the browser was opened. This was also during the days for consumer systems with 16GB max RAM & 32GB on higher end enthusiast systems.

We also have to remeber that this was 10 years before Google removed their “Don’t be Evil” motto, and there was still a great deal of trust that had been earned by tech professionals.

So when Chrome came in, had a minimalist UI (for the time) and was light weight and memory light without any obvious memory leaks, it was a performance boost for a toooon of users.

Chrome has since become a memory hog and is now being developed and pushed by a company that has become heavily enshittified & evil. Firefox has become lightweight, memory efficient, and is an FOSS product that’s not evil and enshittified making it the right choice in 2024, but is going to be an uphill battle that hopefully more tech professionals move to as Manifest V3 becomes a reality.

I switched off of Firefox because of those memory leaks. I remeber when it hit the tech news circles when the community contributer that was frustrated with them went in and fixed two of the biggest culprits.

Then I just didn’t bother til somewhat recently. For the most part, it’s great and does what ilI want/need. Biggest complaint is that some UX overhauls are needed for Mobile FX, especially around tab management.