Bazzite. It’s based on Fedora uBlue so it’s technically Fedora, but being an immutable OS, it works quite differently enough that it counts as its own distro. For instance, you don’t use dnf or yum to install stuff, you’d use Flatpak/Distrobox/Nix. Updates are done using the rpm-ostree command, and it’s effectively a rolling release model, but atomic in nature so you get none of the instability that you’d get in a typical rolling release.
It’s useful for those who are interested in using an immutable OS. An immutable OS has several advantages over regular OSes, such as reliable and atomic updates, easy rollbacks, increased stability etc. However, a major drawback with immutable OSes is customisation - because certain key parts of the system are read-only, you may be limited in what you can change. Fedora Silverblue/Kinoite solves this to some extent by using ostree, and rpm-ostree to install packages in a layered fashion. The problem with that though is that it can significantly increase update times and also bloats up your system, which is a concern if you’ve got a lot of packages installed in that manner. Plus, there’s also the issue of limited customisations - maybe you want to switch to a completely different DE for instance.
This is where making your own custom image comes in handy. When you fork the template, you can put in all your customisations on git, and your custom image gets built automatically.
You have to trust another party blindly not to inject malicious code
But you’re doing that anyway with pretty much every piece of code/app/website that you use without auditing it yourself, so what makes this any different?
In any case, at least with uBlue you don’t have to blindly trust anyone because everything in uBlue is fully open and transparent, you can see for yourself exactly what’s being done - in plain text.
Risk of not being maintained anymore.
Not really an issue. This isn’t a distro, it’s literally just a script which builds your own distro using upstream code, which is pulled from Fedora. So the only real risk is if Fedora decides to shut shop or something. But even if they did, someone else would fork it, and you could just rebase to that fork and move on.
Opera also invented the browser Speed Dial, which was super handy back in the day.
But most importantly, Opera invented tabs, or at least the concept of tabbed browsing. I recall using Opera on Windows 3.11 and for the longest time, even during the Win 9x era, no other app used tabs.
In addition to mouse gestures, they had customisable keyboard shortcuts for practically every browser feature, again, something which very few apps bothered with.
The page compression built into Opera Mini was a life saver on Symbian and Windows Mobile devices back in the 2G/GPRS era. Opera Mini loaded pages blindingly quick and there was nothing else like it on the market, even leading up to early Android days.
but thankfully he started Vivaldi which feels like the spiritual successor.
Too bad he made the unfortunate decision of going with the Chromium engine instead of Gecko, or even making their own engine. I would’ve loved to use Vivalidi if it weren’t for that fact.
look for USB 3.0
USB 3.0 (5 Gbps) is quite ancient by today’s standards. I’d recommend a USB 3.2 Gen 2x2 (20 Gbps) or even a USB 4.0 drive (20/40 Gbps) drive.
I’ve only started using yadm recently so I may not be able to elaborate in detail, but for me the main draw for using yadm (as opposed to Ansible, which I use at work) is the simplicity. It’s basically just a bash script that uses git, so there’s no dependencies besides git and tools installed on most Unix systems. Ansible felt like overkill for what I needed, ie just something to manage and sync my dotfiles.
Also, maybe it’s personal bias, but I really hate installing/using Python-based programs - they often tend to go wild with their dependencies and eventually break. I recall trying to install Ansible on a Raspberry Pi at some point (via pip) and it failed because one of the dependencies couldn’t be compiled for whatever reason. I gave up after trying to fix it for a while, and dropped the idea. I’ve had similar experiences with other large Python projects, there’s always some drama. Why is why I prefer compiled binaries or simple shell scripts like yadm.
I’ve no issues using Ansible at work though. We use it on RHEL so it’s quite stable and doesn’t have the dependency issues you’d get on a bleeding-edge, ever-changing, end-user system. Plus it really shines at the Infrastructure as Code stuff so we use it to automate everything from networking gear to VMs. But I feel it’s overkill for something as simple as syncing a bunch of text files.
Same here. Not just my parents, but also some of my aunts and uncles. None of them are particularly tech savvy and none of them have had any major issues.
People who claim that Linux is difficult to use, or not suitable for newbies, have no idea what they’re talking about.
Ubuntu Christian Edition, if he’s a satanist.
Ubuntu Satanic Edition, if he’s a Christian.
Hannah Montana Linux, if he’s neither of the above.