I also used it and dropped it years ago because it tended to break a lot in updates.
That, their poor kde support, their constant reinventing the wheel (poorly) drove me away.
Now I run opensuse as a rolling distro that’s always up to date and just never breaks even when there are 6000 packages to update. It’s boring and safe.
Most of the GTK environments seem to be doing fine. Most of them seem headed to Wayland as well with the maturity of GTK in Wayland making that easier. Cinnamon will be ready for Wayland in a few months with both XFCE and MATE likely to have something out next year.
Incredibly, GIMP itself may finally get off GTK+ 2. They claim that GIMP 3 will launch in February. We will see how long it takes to get to GTK4. I think the transition will be easier. The jump from 2 to 3 was a big one.
COSMIC of course is going its own way with the Iced toolkit.
On the app side, GTK seems to still be a very popular option.
In terms of conclusions, I do not see mainstream resistance to new GTK versions. Some people balked at GNOME 3 but GNOME today seems more popular than ever. MATE faithfully kept the old GNOME experience but has migrated to newer GTK. It was not a rebellion against the toolkit.
You’re going to have a web browser installed, right? .epub files are just zips with HTML/images/CSS inside. Just find the HTML file with named “toc” and go from there.
What distros are you talking about? Even if install all available DEs, any distro will take ~10 GiB or a bit more. Default installation is much smaller.
There’s no any magic that could reduce Silverblue size, it is based on the same packages as Workstation. Only the installed subset of packages can differ.
Don’t forget part “email notifications”. In addition to configuring the raid, you need to understand when the disk crashed, otherwise the raid will not help.
if you want share files with linux or windows with not basic ways you have many choises. NFS for example, or sshfs if you need folder time to time, or share directory with nginx ( stackoverflow.com/…/how-to-configure-nginx-to-ena… ), or overkill: nextcloud server.
UPD: In general, you just need to find a linux distributive with good documentation and use this documentation for the first time. Some things are solved differently in Linux than in Windows and you just won’t know about it without reading the wiki.
“Do folks in here are really that needy of self-validation, even if it means seeking such from something completely insignificant like internet points?”
But… is that not exactly the description of somebody who complains about downvotes?? As said by others; they should be considered exactly as valid as upvotes. If you feel like they prohibit you from voicing an opinion, I personally feel like that is a you-problem. Ask yourself of the content you posted is crap, if you feel it is not, simply ignore the downvotes and move on, they are just pixels.
Edit: I checked your posts, most downvoted ones seem to be clickbaity or images that you posted to the linux community. This is not something that vibes with that type of community, I would have downvoted that too. The ones on your technical questions seem unjustified however. Posting a code snippet asking people to execute it… I think that crap should even have been deleted by mods.
I would check out your laptop, especially if it’s somewhat new. I have one that is dual booting from an M.2 NVMe drive and a SATA SSD. Even if it didnt, I have easy panels that pop off when I wanted to swap.
On the surface, the biggest difference between distros will be the package manager and the update cadence. Most package managers are generally comparable so I won’t get into that. The cadence has to do with release type - rolling or fixed - and the speed with which updates are released. Do you want the newest packages, LTS or somewhere in the middle? This is probably the first big decision to make when choosing a distro. The only real must-have here is you want a distro that provides timely security updates. Even a highly stable LTS should be pushing out security updates asap.
Then you have default package choices, which are often superficial like DE or default apps. This can all be changed so it’s not much of a concern. But there could also be more impactful choices like whether a distro uses systemd or glibc vs musl. The mainstream distros tend to use systemd and glibc, which is generally good, but know that you have other options if your specific use case requires it. There’s also package availability, meaning the number of packages available in the repository, although this is less important than it used to be because you have options like Flatpak or Nix for getting packages that aren’t in your distro’s repository.
There are also some distros created with a specific use case in mind, such as Alpine for containers or Kali for testing network security.
Finally, you have structure and governance. Some distros have corporate backing, others are community supported and still others aren’t much more than a hobby. The ones with corporate backing typically have options for paid support. In general, you want something with stable and competent governance where it will continue to thrive even as team members change. You can find examples of this in corporate-backed distros as well as community distros.
So your biggest choices are going to be cadence, structure/governance, and whether you may need paid support now or in the future.
As for what distro developers actually do… First, they build the tooling and infrastructure to make their distro work - package manager, packaging tools, repository, etc. Then, they are responsible for packaging everything available in the distro. They are pulling in source code for all these apps, compiling it and putting binaries in the repository. They rebuild packages as required when there are updates to the source code. Some distros like Arch will build vanilla packages, meaning they don’t make changes to upstream code. Others may apply their own patches for various reasons. Some like Red Hat will provide patches to upstream apps requested by customers as part of their paid support services. So let’s say something isn’t working the way you need it for some random FOSS app included with the distro. You can put in a request and they will change it for you.
As for your specific question about simulating Ubuntu on Fedora, that is not possible. They each use their own distinct package manager and repository. They generally have similar packages, but they are not interchangeable. However, there are tools like distrobox and distros like VanillaOS that have mechanisms for using another distro’s packages. These use containers under the hood so it’s not quite the same as just installing .deb on Fedora or .rpm on Ubuntu.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.