Wayland has it’s fair share of problems that haven’t been solved yet, but most of those points are nonsense.
If that person lived a little over a hundred years ago and wrote a rant about cars vs horses instead, it’d go something like this:
Think twice before abandoning Horses. Cars break everything!
Cars break if you stuff hay in the fuel tank!
Cars are incompatible with horse shoes!
You can’t shove your dick in a car’s mouth!
The rant you’re linking makes about as much sense.
Contribute to FOSS software.
Meanwhile Discord misses half the features Matrix has. It’s almost as if they’re different projects with similar, but different goals.
One tries to be a flexible, interoperable, and secure protocol for communication, that’s free for anyone to implement and use…
The other is a for-profit company that cherishes its centralized nature and far reaching control, allowing them to sell you random bells and whistles, collect your data unobstructed, and lure in investors and advertisers.
In case of Gnome it was addressed, just by different people. Gnome 2 continues to live on as MATE, so anyone who doesn’t like Gnome 3 can use it instead.
To provide features that Xorg can’t.
If you don’t need features like fractional scaling, VRR, touchscreen gestures, etc. you won’t notice a difference.
People who do use those, will. Because for them, those features would be missing or not complete on Xorg.
To be honest, most things in Nobra can be installed/done to regular Fedora. And, unlike Nobra, Fedora has more than 1 maintainer: goof for the bus factor.
Almost everything that’s not Gnome can be considered lightweight, to be honest.
OpenSUSE + KDE is a really solid choice, I’d say.
The most important Linux advice I have is this: Linux isn’t Windows. Don’t expect things to works the same.
Don’t try too hard to re-configure things that don’t match the way things are on Windows. If there isn’t an easy way to get a certain behavior, there’s probably a reason for it.
I’ve heard that he passed some of his duties onto other people.
However, I’m not aware of anyone within the team criticizing his behavior or statements, which, while might be a bit of a stretch, likely implies that everyone related to the project, at the very least, tolerates, if not outright shares the the views.
I find it practically impossible to trust claims of people like that, to be honest.
“Accusing with no concrete proof” is exactly what GrapheneOS developers are doing in regards to other projects. Claiming other products are a scam, particularly when those products somewhat compete with yours, is a pretty big red flag.
Reviewing the source code of an entire operating system is not a task doable by a single person, particularly when that person is not an expert in the field.
A proper code audit needs to be done by a team of professionals capable of spotting things like actual security vulnerabilities and logic errors that might result in more data being exposed, than advertised.
Considering the lead developer of GrapheneOS bans anyone from their chat for asking how an Android phone with GrapheneOS compares to a non-android phone, such as a PinePhone or Librem 5, in terms of security, because, according to said developer, PhonePhone and Librem5 are “scam products” and even asking questions about them is “spreading misinformation” and “promotion of fraud”, I’d be quite, quite vary of the claims GrapheneOS developers make about its security.
I have a 120 gig SSD. The system takes up around 60 gigs + BTRFS snapshots and its overhead. A have around 15 gigs of wiggle room, on average. Trying to squeeze some /home stuff in there doesn’t really seem that reasonable, to be honest.
As long as you don’t re-format the partition. Not all installers are created equal, so it might be more complicated to re-install the OS without wiping the partition entirely. Or it might be just fine. I don’t really install linux often enough to know that. ¯\_(ツ)_/¯
You can put your /home on a different BTRFS subvolume and exclude it from being snapshotted.
Not OP, but I have the same setup.
I have BTRFS on /, which lives on an SSD and ext4 on an HDD, which is /home. BTRFS can do snapshots, which is very useful in case an update (or my own stupidity) bricks the systems. Meanwhile, /home is filled with junk like cache files, games, etc. which doesn’t really make sense to snapshot, but that’s, actually, secondary. Spinning rust is slow and BTRFS makes it even worse (at least on my hardware) which, in itself, is enough to avoid using it.
Virtual desktops are arranged on a one dimensional axis. Whether it’s vertical, horizontal or fucking diagonal doesn’t really change how they work. It’s just fluff and animations, really.
There are “Video Rooms”. They’re in beta too.
Also, screen sharing is done via the same platform agnostic web APIs every other Electron-based app uses, though.
I got rid of screen capture induced lag by switching to Wayland.
Dualbooting is possible and easy: just gotta shrink the Windows partition and install Linux next to it. Make sure to not format the whole thing by mistake, though. A lot of Linux installers want to format the disk by default, so you have to pick manual mode and make sure to shrink (not delete and re-create!) the windows partition.
As for its usefulness, however… Switching the OS is incredibly annoying. Every time you want to do that you have to shut down the system completely and boot it back up. That means you have to stop everything you’re doing, save all the progress, and then try to get back to speed 2 minutes later. After a while the constant rebooting gets really old.
Furthermore, Linux a completely different system that shares only some surface level things with Windows. Switching to it basically means re-learning how to use a computer almost from scratch, which is, also, incredibly frustrating.
The two things combined very quickly turn into a temptation to just keep using the more familiar system. (Been there, done that.)
I think I’ll have to agree with people who propose Virtual Machines as a solution.
Running Linux in a VM on Windows would let you play around with it, tinker a little and see what software is and isn’t available on it. From there you’ll be able to decide if you’re even willing to dedicate more time and effort to learning it.
If you decide to continue, you can dual boot Windows and Linux. But not to be able to switch between the two, but to be able to back out of the experiment.
Instead, the roles of the OSes could be reversed: a second copy of Windows could be install in a VM, which, in turn, would run on Linux.
That way, you’d still have a way to run some more picky Windows software (that is, software that refuses to work in Wine) without actually booting into Windows.
This approach would maximize exposure to Linux, while still allowing to back out of the experiment at any moment.