That kinda exists with NixOS, but you'd have to backup your personal files separately.
You're not really backing up the OS with NixOS, but the nix configuration file describes how the OS is built in a reproducible way.
Or do you just remember all the config changes you did and type them out from the top of your head? And all the apps you have installed? It's over 300 apps and 100 config files for me.
Well, kinda. I have have scripts to set up most of my system after an installation. It’s nice so that I don’t have to remember everything I’ve done. It means I can reinstall my system or install on a new system with relative ease.
Doesn’t need to be anything complex. Just having a list of packages I want installed and that I can copy into my terminal makes things so much faster.
Timeshift is completely unnecessary. Fedora Atomic's rollbacking is more powerful and avoids certain issues.
You should only be backing up personal files, not OS files. The OS is replaceable, your personal files are not.
Switzerland has strong privacy laws, but there are still situations where they legally have to comply. Of course, Proton also collects very little data and keeps things end to end encrypted, so even if they have to provide data, it’s not much.
The only issue I've had with LocalSend is that it's a bit buggy on iOS. If you leave the app open in the background and go back to it, it won't be able to receive files. I have to force quit it and open it again to fix it.
Clickbait. The VP Engineering for Ubuntu made a post that he was looking into using the Rust utils for Ubuntu and has been daily driving them and encouraged others to try
It’s by no means certain this will be done.
Overall, I don't think Mozilla is wrong. Without the Google Search deal, Firefox will have less resources to build a competent browser.
But Mozilla has also done a poor job at becoming financially stable without this search deal. It also doesn't help that Mozilla's CEO's salary keeps going up in spite of the declining market share.
It would have been nice is Mozilla was able to fill a niche like Proton: building a suite of secure and private services. But instead they're moving towards advertising.
Before Wayland, there was X Window System, created in 1984. X Window System was designed in a time where you had one good computer connected to multiple displays used by different people. X went through many versions but version 11 (X11) stayed around for a long time.
But the architecture just isn't good. It wasn't designed for modern needs. MacOS used to use X, but replaced it to fit modern needs. Windows didn't use X, but they too updated Windows to fit modern needs. But Linux and other OSs stuck with X for a lot longer, hacking it to make it work. Honestly, it's amazing how well it does work.
But isn't not great. It wasn't designed with security in mind, it doesn't do multi-monitor well. Behind the scenes, it considers everything to be one giant display; issues arise when it comes to mixed-dpi displays and when monitor refresh rates don't match. It's also just a bloated, old code base that people don't want to work on. Fixing X would not only be difficult, but would break compatibility.
So people got working on a modern replacement for X aiming to avoid its issues. Wayland is leaner, more opinionated, and designed for how modern hardware operates. Wayland itself is just a protocol (like X11), and there's many different implementations of that protocol: Mutter, Kwin, wlroots, smithay, Mir, Weston, etc. Meanwhile X11 pretty much only had one relevant implementation, Xorg. Wayland's diversity has its pros and cons. Pros include (1) you can create your implementation in any programming language you want rather than being stuck to just one, (2) an implementation can fill just the needs on the person making it rather than trying to generalize it for everyone. But cons include the fact that this fragmentation leads to scenarios where one implementation supports something that others don't and implementation-specific bugs.
Wayland's opinionated design is also draws criticisms. It gives a lot of control to the compositors rather than windows, which is how Xorg, MacOS, and Windows work. Nvidia's wayland adoption was also slow and terrible. It took many years to get it into the only decent shape it's in now.
That was there before 133, don’t remember the exact release that added it.
I don’t get why this sort of picture always gets posted and upvoted when it’s wrong for most distros nowadays.
Blender's Wayland support is not great because they're doing stuff from scratch. They're not using an existing toolkit like GTK, Qt, Electron, or even something like SDL to get Wayland support.
But if you're using an existing toolkit things are much easier and support is automatically there, you just need to do testing to ensure everything works.
The common biggest things that still use Xwayland are Chromium based apps and programs running under wine/proton. Chromium has an experimental Wayland mode that works well enough, but definitely has some bugs, especially around windowing. Wine Wayland is in the works.
Yeah. I’ve used NixOS and think the idea is cool, but overall I prefer Fedora Atomic. Unlike NixOS, it’s a complete OS out of the box and is less quirky than NixOS. Though I am a proponent of Flatpak, those who don’t like it will have a very different opinion of Fedora Atomic.
I just wish Fedora Atomic was more declarative and that bootc could work a bit closer to how NixOS's nix.conf worked. I would love if that there was a a container file could be declared and used built similarly to nix.conf is (avoiding the user manually building the and signing the container file).