It's a way to go at least for rolling release. However, tw is looking less and less interesting than it used to 5 years ago now that all these shiny new immutable distros are coming out.
For me searxng hasn't been working (tried multiple instances, throws mixed errors). I've been using whoogle and it works pretty well.
I feel like this ruins the aspect of an archive of information where users can go back through and find useful info similar to SO in a way. Maybe there will be a meta search engine for looking through all of the popular instances?
I'm pretty sure sid also has package freezes for when it moves up to testing. In general Debian's purpose is as a stable distro and it might be better to use a distro that focuses on rolling release for bleeding edge packages.
Can windows also break grub on gpt or only legacy mbr?
Flatpaks really have the added benefit of things just work. Many distros have problems with codecs for example and need to install extra packages to get video working in Firefox. The flatpak version doesn't require any of this and you can just install and move on with your life. Yes dependencies are "redundant" sometimes but you have the added benefit of a really clean base system without hundreds or thousands of lib or dev packages. Also sometimes you need a specific version of a dependency. Let's say you need to update it for compatibility with a specific package but that breaks another which needs an older version. The system can stay especially clean when it comes to the toolbox utility and dev environments (this is available in other distros as distrobox I think).
Tbf all of those distros except for manjaro are based on Ubuntu, so you really are more like hopping DEs and defaults more than distros. Also, I always tend to prefer the main distro than the spin-offs, so if you are using all of these smaller Ubtubtu-based distros that are breaking why not try Ubuntu itself? It has a much larger userbase and is tested more with more documentation.
Immutable OS's like fedora silverblue tend to prefer flatpaks due to the read only nature of system files. Yes, you can rebuild the image and layer the rpm package over the rest of the system, but that's really supposed to be kept to a minimum.
Yup, that seems what it is. Thanks can't believe I couldn't figure that out myself ๐ .
I used it on my gaming rig for about a few months before giving up due to frustrations with nvidia ๐. I guess it's not considered distro hopping because I was forced to hop back to windows. Never had any other issues besides nvidia. I've only ever used rolling release distros and the problems I had to deal with on Arch for example never came up in Tumbleweed.
OpenSUSE Tumbleweed. It's surprisingly stable for a rolling release distro.
No, I am using fedora silverblue which is point release. But there are rolling release immutable distros like opensuse aeon/kalpa im pretty sure. Basically the system files are read only and packages are "layered" onto the system image through transactional upgrades. Most of the packages you want to install should be in containers like flatpak (for gui) and distrobox (for terminal). This keeps the base system clean and small and doesn't get "bloated" like other mutable OS's.