Holly brings three decades of invaluable experience in nonprofit management, having served as a consultant, director of development, executive director, and board member for numerous organizations. Notably, she founded the nonprofit organization Artists United, dedicated to empowering individual artists and fostering collaboration across artistic disciplines for the collective good. Additionally, Holly served as the Executive Director of the BioBricks Foundation, an international, open-source biotechnology nonprofit.
Lots of tools ignore xdg, and issues asking to add support get bogged down in backwards compatibility problems. The best they achieve is to introduce yet another env variable to control where the config goes. It’s really annoying.
I have a bunch of TOOLX_CONFIG=“$XDG_CONFIG_HOME/toolx” stuff in my bashrc.
Tbh, I don’t really get the hate that Ubuntu gets.
I mean, I do understand that people don’t like some of the decisions made with Ubuntu (e.g. snap), but especially for people who don’t use an OS for the sake of using that OS and just want to use their PC to get stuff done, Ubuntu/Kubuntu are quite good.
You have a mostly consistent UI that can do most important configs without touching CLI. Manuals and simple guides are easy to find, even in other languages than English (which is important for quite a big number of people outside the US).
And contrary to some other, smaller distros, Ubuntu isn’t run by just 1-2 people and you can trust in it still existing in 10 years. (Obviously, this is true for many other distros, but some quite widly used distros are run just by a tiny team of hobbyists)
I mean, I’d get the reaction if someone claimed they are Linux users because they use Android (though with enough knowledge you can also get a full Linux distro running on Android in chroot).
“Use Snaps”
“No” (installs .deb)
“Fuck you, use Snaps”
(The Snap Store is a proprietary closed-source black-box that updates your snaps without asking and every part of this statement was a deliberate planned feature by Canonical)
I looked into it. You’re right.
They implemented the ability to permanently hold all automatic updates.
After five years of debate during which they consistently claimed that the whole point of Snaps is that developers can push whatever, whenever.
I mentioned this in the comment you answered to. But as I said, this might be an issue for people that use Linux because they really hate anything that isn’t GPL, but 97% of the people on this planet care more about whether something is simple to use than what license it uses, as evidenced by the market share of Windows, Android, Chromebooks and Apple products.
Wouldn’t it be better to get some of them to use Ubuntu with snaps than to stay on their proprietary platforms, because packet management sucks and conflicts are basically impossible to solve for someone who’s not a software developer?
Linus swore that Bitkeeper wouldn’t alter the agreement further, like a mad egotistical movie villain.
Canonical is very clearly funneling their userbase towards a Snap-only environment (something that already exists as an option).
As the sole keyholders, and as a for-profit business, what is the next step?
Is it to maintain a wealth of options, even when that cuts into profit margins? What about when those options are competing products (think Gnome and KDE back in the Unity days)?
These things just do not make sense from a business perspective, and they will not be necessary once their userbase is locked into the Snap walled garden.
As to your point about licenses and market share, default non-options and limited choices aren’t compatible with conversations about choice.
I really don’t like that sentiment though. Software development isn’t for free just because you slap GPL on it. These devs need to be paid somehow if they are supposed to do more than 3h/week.
You can also see the same thing in the Linux kernel. Many Kernel devs are employed by Microsoft, Google, the NSA and many other commercial entities.
Oldest developer trick in the book. Program in a bunch of useless delays everywhere. On the next few updates, slowly remove them and say you are "improving" the system.
Linux users constantly talk about how Linux just works and Windows is garbage, but then half these comments are talking about how you should buy an entirely different computer to make Linux run with FEWER issues.
Windows may have it’s problems, but I don’t need to buy an entirely new PC to make it work. AMD, Nvidia, Intel, doesn’t matter. It just works.
This thread is utterly braindead but nvidia users are not completely out of luck. Use the proprietary drivers with xserver instead of wayland and it works fine (speaking from personal experience). Xserver has it’s own issues and will probably be phased out in favour of wayland in the future but hopefully by then, it will be able to support nvidia better.
Can anybody who has actually used Nvidia with wayland in the last 6 months tell me what problems you have? As a recreational PC user I have noticed 0 issues with my setup:
Ryzen 3600
Nvidia GTX 1660
Arch
Nvidia-open driver
Gnome / KDE / Hyprland (currently Gnome) running on wayland
I came from Windows 2-3 months ago, my daily usage has been more or less unaffected, especially when it comes to something I could pin to specifically nvidia + wayland.
All the above just makes it seem like nvidia + wayland bad is just a circlejerk.
I used KDE with Wayland briefly a few months ago. The right-click menu would look very glitchy. Items disappeared until hovered over, and then disappeared again when moving the mouse. Firefox also had some issue where it would only take half the screen.
Interesting, but I doubt this was an nvidia + wayland problem, or if it was, it had been since fixed. My first DE was KDE and I used the regular nvidia driver with it, for sure did not notice anything wrong with right click menus.
I would ask whether you realize you're on a linux community, but you referred to a man page as a wiki article so you are clearly lost.
The first paragraph past the link is a summary of the function of the program.
fstrim is used on a mounted filesystem to discard (or "trim") blocks which are not in use by the filesystem. This is useful for solid-state drives (SSDs) and thinly-provisioned storage.
Linux 5.12 rc1 had a bug that wiped mounted file systems. 3.13 was the kernel used in a picture of a computer running Ubuntu 14 on the International space station.
Remember that AI answer that said that adding -f option was to get a confirmation before deletion ?
I’m a bit concerned that this kind of meme will get a lot more real when people will blindly trust AI for commands.
Unfortunately I couldn’t find the post in question but if I recall it was GitHub AI telling boldly that you can add -f to your RM command to get a confirmation…
linuxmemes
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.