I still think the catgirl paws salute should be the new salute of the American Résistance.
I also think the catgirl paws salute should be recognized as a salute.
this post was submitted on 26 Nov 2024
454 points (97.7% liked)
196
16588 readers
1929 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 1 year ago
MODERATORS
I work in tech, and I don't understand people's obsession with having all their RAM free at all times.
If you don't use it, why do you have it?
Windows (not the best OS, but the one I know the most about), will lie to you about how much memory you have that's free. It puts data in RAM as cache. In the event you need that data, it's already loaded in RAM. Usually this is stuff like DLLs and executables for programs.
There's a difference between "free" memory, and "available" memory.
In addition, RAM is always going down in price, so 32G today costs what 16G did, some number of years ago. The same can be said for 16G vs 8G, etc. Though, the comparison becomes less relevant as you get into much smaller and older memory types, since the cost per dimm will only ever go so low.
Buy the memory, use as much of it as you can, as often as you can. Go wild with it. Enjoy.
Use all the RAM you want, but if another program needs it give it back ffs!
For me there are programs that "can acceptably use that much RAM" and those that it's "unacceptable", to me. what's 20% to 40% of my gaming rig's resources may be uncomfortably taxing and laggy for my laptop. Its okay to waste resources on my gaming rig but the laptop needs all it can get. I accept some software will not reasonably run on the laptop. My employer has stuck me on 10yo hardware before, running windows 10 pro + intrusive expensive antivirus and nobody is around to question why their computers are getting 5-15fps and locking up for a minute or two when you open chrome. It becomes normal. Any software is the host and/or backbone for other running software should focus on reducing it's own resource usage for the sake of its children.
Hating furries is already really cringe, but even more so when you have an anime profile picture. At that point it feels hypocritical.
Me when I take a joke seriously.
6 gig of ram on a browser!? wtf people close your old tabs.
Exatcly do it correctly and use multiple browsers each for a very specific type of work/thing you do you animals.
Why the fuck is fuckin censored hut stuff like tailplugs not xD, what a fuckin bull shit.
Already chossed the plug kind
I mostly use Firefox when I use a browser (App-using zoomer) but I actually might swap to something Chromium based at some point? My only reason for it is the resentment I'm building up for Firefox while writing Playwright tests at work. It takes like twice as long as chrome and keeps flaking due to random timeouts ughh
furryfox :3
Source: https://xenia.chimmie.k.vu/ (She has more art, I recommend checking it)
Would be cool if people actually used this as a replacement to their Firefox icon, or if there was a Firefox fork that used this itself for it.
I do!
And I fiund this guide to put it into the new tab page, though I haven't tried to do so: https://this.squirrel.rocks/ff_newtab_logo
Really cool, though personally I would've resized the image slightly so that it would be the same size as the OG Firefox logo.
JUST BECAUSE I USE FIREFOX DOESN'T MEAN I'M A FURRY!
I mean, I am a furry.
BUT NOT BECAUSE I USE FIREFOX!
Bro has an anime profile pic and acts like he doesnt already have the tail plug in smh
Not only that, but the character in that profile pic often sprouts cat ears when she has strong feelings.
Hating furries is stage 1 of becoming a furry.
Soon the world shall be furries. And finally there will be peace on earth.
amen.
(although reasonably i think you might have too much faith in us. a society wide desire to be a colorful dog has the power to accomplish a great many things but peace on earth is a tall order)
Nah, I dont hate them. I don't think I'd be enthusiastic about a full like mascot level fur suit during sex, but cat ears and tailplugs are adorable.
I haven't heard somebody use the word "murring" in like a decade. Methinks they're farther down the pipeline than they want to admit.
- The Internet is full of old memes that slowly make their way around to different communities and this could be one of them.
- What in the world is "murring"? This is the first time I've ever heard of it.
load more comments
(3 replies)
Listen using Firefox doesn't make me a furry.
I mean I am but that's not why.
I switched back to Firefox over a year ago and I have not noticed it using much less RAM than Chrome tbh. It's definitely the better browser for all the other reasons, but I wouldn't list memory utilization as a big advantage over other browsers
Most browsers these days have issues with high RAM usage, and memory leaks to. I'd recommend trying to limit the RAM of the browser, it stops it from eating up so much.
Here's how I did it on linux. I'm sure there's a way to do it if you're on Windows though (might not be as good though).
Desktop file to limit Firefox to 8GB of RAM
[Desktop Entry]
Version=1.0
Name=Firefox RAM limit 8GB
GenericName=Firefox Ram limit 8GB
Comment=Limit RAM for Firefox to 8GB;
Exec=systemd-run --user --scope -p MemoryLimit=8G firefox
Icon=firefox
Type=Application
Terminal=false
Categories=Utility;Development;
StartupWMClass=Firefox
This is a script to limit Firefox to 8 gigabytes of RAM, you may change it lower or higher depending on what your needs are by changing the number from 8 to whatever else you'd like. Fair warning though setting it too low will cause Firefox to lag very badly, and will crash chromium browsers outright (Ask me how I found out).
The whole RAM thing is way overblown. Both browsers request a lot of RAM allocation, but only actually use a fraction of it. When the OS needs it for another process this "allocated, but unused" pool is the first to get used when "Free and unallocated" is gone
Problem is windows reports it all as the same in the task manager so people see that "70%" usage and freak out.
Tl:Dr Windows task manager is a fuckin lier.
There’s also the idea that free RAM is somehow a good thing. In an ideal system, the RAM would always be “full” of potentially useful data. Having a bunch of empty RAM means that it’s not being useful. That space could be used to hold plenty of regularly used files that would be instantly loaded instead of having to pull from the drive again.
I don’t know when everyone started getting concerned with RAM usage, but in a perfect system, it would hold onto all of your frequently used programs and files that it could fit from boot and then those would load instantly.
Some Linux distros even allow loading the entire OS into RAM for wild speeds.
Idle RAM is just that. It does you no favors. Now, I do understand that you don’t want to be completely out, but we act like having 80% free is a goal for some reason.
Having programs steal or sit on RAM without using it is never a good thing. That's why it's called a memory leak, because it's as if the free memory is leaking away. And it gets deprived from other apps that might need it more than Firefox or chromium does.
Your idea only works if programs actually take only as much ram as they need and give it back when done, but they don't do that, they usually sit on it until it's pried from their cold dead fingers. That's what memory leaks are, and modern browsers these days are extremely prone to them.
Unused RAM is wasted RAM. It consumes the exact same amount of power whether there's useful data in it or not. Any self-respecting operating system will fill up RAM that applications aren't using with frequently accessed files, so they're ready to go in an instant.
I think that's precisely why limiting RAM on apps like Chrome or Firefox is so necessary, these apps never release their RAM when they are supposed to, they hoard anything that isn't free and don't give back when it's needed, which is why in the reply to the top comment I shared a desktop entry to limit RAM on Firefox or whatever app you so choose.
Oh, I totally agree. Being afraid to call out to the allocator because "hey, I might need that memory later" is kinda not great. To a certain extent I can see how if an application tends to thrash memory, making a kajillion syscalls might hurt performance, enough that on many machines the gains from doing a single big allocation on the system and then slicing it up into small allocations in-process might outweigh the downsides, but still...
load more comments
(3 replies)
view more: next ›