Do one of the following:
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.
I’m an American, I won’t get the luxuries of the EU court rulings.
And you’ll have a choice to not install them. Or to install versions that you know how they were trained and have guardrails you approve of.
Give Trump the Boote [BOHT]!
👻 ➕ 🗳️ 🟰 ⛵
I mean, technically, contrails are composed of chemical compounds. Mainly dihydrogen monoxide which is one of the most dangerous chemicals there are!
That’s because the anti-Biden propaganda coming from Russian bots & alt-right astro-turfing is effective.
The astro-turfers are everywhere (including the fediverse) , and a ton of them present themselves as “concern trolls” since it’s a little harder to identify them that way.
Yes, an article written by a podiatrist, peer reviewed by a podiatrist, and completely cites their credentials, sources, and reference materials.
Just because you don’t think it’s credible, doesn’t make it not credible.
I mean, you could have easily searched “how much do feet sweat per day” and verified this yourself.
But ok, here’s one of hundreds of the results from podiatry clinics that say roughly the same thing.
Feet sweat. A lot. Like a pint (450g) of sweat a day or more if particularly active or you have larger feet.
So for me, daily at the least. On particularly active days, multiple times.
As somebody that’s been working on computer hardware since the early-to-mid 90s, installing the drivers before connecting the printer was the norm. It was actually the norm for most peripherals. Just be glad you didn’t have to do manual irq assignment. Hell, that is probabaly the issue, is that the driver installer borked the irq assignment when the device already had a handshake agreement with the hardware.
I digress though, this shouldn’t have been the pattern for a modern printer in 2007, when PnP had been standard for several years at that point.
You can buy DRM free books @ your local book store.
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.