

18·
24 days ago2025 is deemed the year of layoffs
Wasn’t 2023 the year of layoffs? Didnt like half a million people get laid off since 2020 per layoffs.fyi?
2025 is deemed the year of layoffs
Wasn’t 2023 the year of layoffs? Didnt like half a million people get laid off since 2020 per layoffs.fyi?
Sucks. Fuck KYC now and forever
He’s using windows.
But while we’re on the subject, ~/.local/share is cancer and shouldn’t exist.
The appropriate path is /usr/share.
EDIT: Okay to be clear I mean that anything that could be global should go into /usr/share and massively save on space and effort if another user needs the same stuff.
Anything that doesn’t need to be global doesn’t need to go into /use/share but somewhere else in ~/.
The way it is now my ~/.local is a massive dumping ground of crap from configs to static app resources that should go into /usr/share to entire applications with snap or flatpak (why I don’t use them) to random config files.
It’s just a nasty mess on my home partition when it in most cases really doesn’t need to be.
Users below rightfully pointed out many exceptions like venvs and while I still believe there should be a more correct place for them to go e.g. (~/.venv, ~/.flatpak), but obviously they shouldn’t go into /usr/share willy-nilly.
I have removed the sass below because I should’ve been more comprehensive in my criticism before ad-hominem.