he/him

  • 1 Post
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle










  • Sounds awesome, at least in theory. It remains to be seen how much interest there is from Publishers.

    I’m hoping he could revive some of the really old and poorly working Linux ports as well as games that barely run on modern Windows or Wine these days.

    Although in practice I can’t think of any game in my library that is in need of such a refresh, they generally all work decently in Wine (and modern Windows) even if some have a broken Linux port.

    Edit: Maybe this is more exciting for macOS as there are plenty of Mac games that remain 32 bit only and thus can’t run on Catalina and above (also who knows how long Apple will keep OpenGL compatibility and Rosetta around). And on mac you can’t just simply “run the game with Proton” instead.

    Also as another thought, while the Linux port requirement is of course a plus for us, it might be off-putting particularly for publishers that have their own shitty stores / launchers without Linux support.



  • Can we stop shaming people who buy NVIDIA?

    For one, people want to keep using what they have and not buy something new just because it may work better on Linux, abd they may not even be able to afford an upgrade. They probably didn’t even know about Linux compatibility when they got it.

    And additionally, some people have to use NVIDIA because e. g. they rely on CUDA or something (which is unfortunate but not their fault).

    And honestly, NVIDIA is fine on Linux nowadays. It sucks that support for older cards will likely stay crappy forever but hopefully with the open kernel drivers and NVK newer cards won’t have to suffer that fate.


  • Basically none of your current software works out of the box (you’ll need a special Xorg implementation that works with your Wayland implementation in order to run non-Wayland applications).

    I’ve never seen any distro with Wayland that didn’t have XWayland set up and working out of the box, so that’s not something the end user needs to worry about. And “Basically None” is also not true anymore. Practically anything made with GTK3/4, Qt5/6, SDL2, recent Electron versions etc. natively runs on Wayland. It’s mostly games, Wine and a lot of proprietary software that doesn’t.

    Most applications are specific to your Wayland implementation instead of a general application that runs in all environments.

    Wdym by that exactly? I mean, a KDE application will run just fine on GNOME or Wlroots compositors.


  • There are several remarks in that article that bothered me. I agree with their message overall and am a strong proponent of Wayland but…

    Unless your workflow (and hardware) comes from 20+ years ago, you have almost no reason to stick with Xorg

    There definitely are valid use cases that aren’t 20 years old that will keep you on X11 for a little while longer. And hardware too: NVIDIA dropped driver support for Kepler GPUs and older before they added GBM support which is effectively a requirement for Wayland, so you can’t use these older cards on Wayland with the proprietary drivers

    Of course, NVIDIA likes to do their own thing, as always. Just use Nouveau if you want to do anything with Xwayland, and you don’t have several GPUs.

    Uh, no. Nouveau is not a serious option for anyone who likes using their GPU for useful things. And on those older cards it will likely never work well.

    The author of that article seems extremely ignorant of other people’s needs.


  • I have a laptop with hybrid Intel+NVIDIA graphics, and I can say that offloading games and such to the dGPU while letting the iGPU handle everything else works with zero issues for me on Wayland.

    On desktops where the NVIDIA GPU handles everything I don’t have that much experience on Wayland although when I did try it earlier this year it was surprisingly good, but with occasional dumb bugs like Plasma panels freezing or XWayland apps breaking in funny ways. Although honestly just a few years back running Plasma X11 on NVIDIA wasn’t much better than Wayland now.



  • I switched to Wayland over two years ago and these days I don’t look back at all. I don’t care if Wayland has full feature parity with X11 as long the features I actually use are supported which they are.

    Clipboard sharing in VirtualBox doesn’t work right now (though I’m relatively sure it could be implemented by VirtualBox right now with Wayland as it is) and neither does AutoTyping in KeePassXC (not sure if there’s a mechanism for that on Wayland), though Autofill in the Browser works so it’s no big deal to me.

    In return I get 1:1 touch gestures, better multi monitor support and an overall smoother desktop on Plasma Wayland so I’ll take it.

    People often still make complaints about Wayland that have been fixed months or years ago and it’s a bit tiring.




  • I have a feeling they’re slowly but steadily moving from deb packages to snap-only completely. Because unlike what Mark Shuttleworth said when they abandoned Unity, Canonical doesn’t let their users decide which technologies should catch on. The Linux desktop as a whole is moving to a Flatpak future for desktop apps, yet Ubuntu keeps pushing Snaps down their users throats whether they want it or not and sort of “fight” Flatpak on Ubuntu spins.

    I get it, Snaps are more versatile than Flatpak, you could make everything on the system a snap (can’t ship a DE or the kernel as a Flatpak now, can you) and CLI programs as Flatpaks also suck compared to snap (and distro packages obviously), but for desktop apps Flatpaks are just the obvious choice and the Linux community has shown that.

    I’m waiting for the day where you can install Flatpak as a snap on Ubuntu lmao