The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
yea wayland is fucking painful to deal with sometimes. (speaking from experience much like everyone else who's used wayland)
if it had some kind of translation/backwards compatibility with these kinds of libraries/programs (beyond xwayland allowing x11 apps in a wayland session) then the transition would be a lot smoother and eaiser for everybody.
but no, that makes too much sense and the fuckwits over at wayland will just ignore you.

sometimes i do wish there was more standardization and communication in the world of linux. shit like this wouldn't happen.
 
As the forum's resident GNOME user, here is why I like it:

* Its workspaces model is more accessible and intuitive than any other virtual desktop model I have ever seen on any DE or OS. It feels like an integral part of the DE instead of a tacked-on afterthought.
* It is keyboard-driven to an extent that is only beaten by tiling WMs, without all the autism that is required to effectively use a tiling WM.
* It is prescriptive about its workflow, but once I got used to it, I found it was effective for me. I have found that I don't care about not being able to minimize windows. I can shove them off to another workspace. Likewise, I don't need a dock or desktop icons, I just hit Super and start typing what I want. In general, it feels like it gets out of my way and lets me focus on following lolcows and writing shitty code.
* The unified search is so much better than anything else in the Linux realm and it's not even close.
* GNOME built-in apps have a more unified look and feel than KDE apps. Also, in my opinion, with some notable exceptions, GNOME's built-in apps tend to be generally more capable and easier to use than KDE apps. Related, GTK is, in my subjective opinion, a more aesthetically pleasing toolkit than Qt.
* Vanilla GNOME is more stable and less buggy than KDE.

What I don't like about GNOME:

* The exceptions to the above point about GNOME apps being better than KDE apps: Dolphin and Konsole are better than GNOME Terminal and Nautilus. The gap has narrowed between Dolphin and Nautilus, and GNOME Console has promise, but the file manager and the terminal are the two most important built-in apps, so GNOME's deficiencies here will always be a problem.
* Extensions... yes, they suck in GNOME. Though I don't mind the vanilla experience, there are still some gaps that I would like extensions for. However I gave them up due to the instability they create.
* The GNOME dev community is cringe as fuck.
 
never did understand why gnome is so popular, its stable and relatively bug free to give it credit but (in my opinion) with how limiting it is, its more or less just OSX's interface but for linux.
This is honestly why I don't know shit about GNOME and am basically ignorant on the subject. Any time I've had to deal with it, it's been a matter of minutes before I tard-raged and did anything possible to avoid it. That's probably why my last couple posts on the subject have been absolutely retarded.

My hatred of it doesn't come from reason, but experience (and as little of it as humanly possible).
 
This is honestly why I don't know shit about GNOME and am basically ignorant on the subject. Any time I've had to deal with it, it's been a matter of minutes before I tard-raged and did anything possible to avoid it. That's probably why my last couple posts on the subject have been absolutely retarded.

My hatred of it doesn't come from reason, but experience (and as little of it as humanly possible).
same, my first linux experience was on ubuntu back when it used unity. tried gnome years later and really didn't like it. when i do eventually swap to linux, plasma is gonna be my desktop.
xfce was a contender and is nice but i prefer plasma to be honest.
 
I've finally made my first full Arch install on my laptop. I wanted to have full disk encryption with hibernation, TPM and Secure Boot, and I found the best way to proceed:
  1. Set your SB policy to Config mode
  2. Make two partitions, an unencrypted boot/EFI volume and a LUKS-encrypted LVM volume. I set a temporary password for testing and installing.
  3. Add your system and swap volumes to the LVM partition.
  4. Install Arch 8) Make sure you install GRUB with "tpm" module.
  5. On your Arch install, generate your SB certs with sbctl, then enroll them on your BIOS. Make sure to sign GRUB and vmlinuz images with it
  6. Reboot to BIOS, then activate Secure Boot
  7. Install and setup Clevis, add a new LUKS key to your partition, and enroll it to the TPM. Make your changes to your mkinitcpio.conf, rebuild the images then reboot.
  8. For hibernation, make sure you actually mount the goddamn swap partition instead of waisting an afternoon
In short, I learned that hibernating to a LVM block just werks.
 
This is honestly why I don't know shit about GNOME and am basically ignorant on the subject. Any time I've had to deal with it, it's been a matter of minutes before I tard-raged and did anything possible to avoid it. That's probably why my last couple posts on the subject have been absolutely retarded.

My hatred of it doesn't come from reason, but experience (and as little of it as humanly possible).
My GNOME experience:

"Oh, this program is pretty cool." [5 minutes later] "Now where in the GUI settings would I adjust this?" [30 minutes later] "Okay, it just doesn't have any settings."
 
My GNOME experience:

"Oh, this program is pretty cool." [5 minutes later] "Now where in the GUI settings would I adjust this?" [30 minutes later] "Okay, it just doesn't have any settings."
Usually when I'm installing a new distro:

"My LiveCD session just booted and oh... it's Gnome. Back to the drawing board."
 
ive been watching this guy mashed and hes shown off some cool tiling window manager stuff what are you guys thoughts on that over DEs?
I use i3 but I don't do a whole lot of tiling, I use it because it's at least sort of maintained, but unlike sway, is not written by a weird critical constructivist and is going to delete my files. Or not, feel free to kill my hope.
 
Could never get into tiling window managers. Felt unnatural. But it's impressive when someone can do it well.
 
Oh by the way, if you need to merge two directories that are on the same drive and don't want to needlessly copy them, cp to the source directory then input find -type d -exec mkdir -vp "$DEST"/{} \; -or -exec mv -nv {} "$DEST"/{} \; where $DEST is the destination. Saved me hours of copying when a mergerfs.rebalance went wrong (I had an unused mountpoint that got populated, and then made a directory location mistake when using rsync)
 
Oh by the way, if you need to merge two directories that are on the same drive and don't want to needlessly copy them, cp to the source directory then input find -type d -exec mkdir -vp "$DEST"/{} \; -or -exec mv -nv {} "$DEST"/{} \; where $DEST is the destination. Saved me hours of copying when a mergerfs.rebalance went wrong (I had an unused mountpoint that got populated, and then made a directory location mistake when using rsync)
Couldn't you just use rsync to do the same thing?
 
As we roll into 2024, Wayland sadly is still proving to be a divisive topic with some frustrated with it either from past experiences or not all software yet being fully adapted to make use of Wayland directly with all available features. There's also some still hoping for an X11 renaissance that will never materialize. Well known KDE developer Nate Graham is out with a blog post today outlining his latest Wayland thoughts, how X11 is a bad platform, and the recent topic of "Wayland breaking everything" isn't really accurate.

Nate Graham acknowledges current gaps in Wayland support but on the matter of "Wayland breaks everything" isn't really the right perspective:
"Look, if I said, “Linux breaks Photoshop; you should keep using Windows!” I know how you’d respond, right? You’d say “Wait a minute, the problem is that Photoshop doesn’t support Linux!” And you’d be right. It’s a subtle but important difference that puts the responsibility in the right place. Because there’s nothing Linux can do to ‘un-break’ Photoshop; Adobe needs to port their software, and they simply haven’t done so yet.

And it’s much the same with X11 and Wayland. Wayland wasn’t designed to be a drop-in replacement for X11 any more than Linux was designed to replace Windows. Expectations need to be adjusted to reflect the fact that some changes might be required when transitioning from one to the other."

He goes on to share his thoughts on X11 being a bad platform, the real platform these days being more about Wayland / Portals / PipeWire, and more. He concludes his remarks with:
"In this context, “breaking everything” is another perhaps less accurate way of saying “not everything is fully ported yet”. This porting is necessary because Wayland is designed to target a future that doesn’t include 100% drop-in compatibility with everything we did in the past, because it turns out that a lot of those things don’t make sense anymore. For the ones that do, a compatibility layer (XWayland) is already provided, and anything needing deeper system integration generally has a path forward (Portals and Wayland protocols and PipeWire) or is being actively worked on. It’s all happening!"

Head on over to Nate's blog for his Wayland thoughts if you still are unsure about Wayland taking over of the Linux desktop that we'll hopefully see improve greatly over the course of 2024.
Link

I’m a little torn over Wayland. I like that it has no screen tearing but it doesn’t feel ready.
 
Back