You are viewing a single thread.
View all comments View context
10 points

GTK, Qt, Firefoxes XUL, Electron (Chromium), Iced, and more support Wayland. You dont develop apps for Wayland, you develop them with a GUI toolkit.

permalink
report
parent
reply
14 points
*

Fair enough. All I know is to get something as simple and necessary to my workflow as using KeePassXC, I had to adjust a few QT flags in my environment variables. No big deal as I actually enjoy configuring my system, but it’s in my opinion Wayland will be “ready” when this sort of under the hood tweaking won’t be necessary by the user.

Here, I’ll pose a simple question that kind of gets at the heart of what I’m talking about. Libreoffice works great on Wayland right? Good, fantastic, kudos to Libreoffice, kudos to Wayland. Now, name me a 2nd office suite that works on Wayland. Just one. This is a genuine question and despite my decent google fu, I can’t find a one. I got Open Office to open on Wayland, but it doesn’t recognize the entire suite.

Now, this may seem like an unfair argument to make, as there were never many office suites available on Linux to begin with. And there’s always been people in the Linux community who will call for more uniformity, but I, like many others, love Linux for it’s extreme customizability (amongst other reasons). Wayland severely cuts down on my choices of what TWMs I can use, what DEs are available, and various widely used productivity tools like office suites.

The amount of knots Wayland enthusiasts tie themselves up in to say “but if you just configure this flag, if you just run this through xwayland/game scope, if you just don’t use nvidia, then wayland is ready” is just pointing to the fact that it’s straight up not.

And that’s not the fault of any one entity. Writing a protocol like Wayland is a massive endeavor and is needed. But developers across the board who want to provide support for Linux, are now scrambling to rewrite parts of their applications to conform to this new protocol because yes, they see the writing on the wall (especially with the latest lines in the sand drawn by Red Hat). But isn’t the fact that their scrambling to get this accomplished, and convert their apps to Wayland, an indicator that maybe, just maybe, that Wayland as a daily driver for, if not the majority, at least a reasonable part of the Linux community, not ready?

I’m not saying Wayland isn’t the future. What I’m saying is until discussions like these are the outlier, not the norm, Wayland isn’t ready.

permalink
report
parent
reply
4 points

the calligra suite works fine too. open office is basically dead and replaced by libreoffice. I don’t know if any development is still happening. I can’t name another office suite Wayland or otherwise though

xwayland does just work though. I don’t even know how to explicitly run something under it

explicit flags are more of a problem, but they’re going away slowly, and for the most part people can just let things run under xwayland instead of dealing with flags. there are some apps that just won’t work, but for the most part it’s not a widespread issue in my experience

permalink
report
parent
reply
2 points
*

.Uhm…

What did you need to set for KeepassXC? The flathub version and fedora RPM just work.

You can modify flatpak permissions easily in KDE or using Flatseal though, to remove a lot and especially restrict keepassXC to only readwrite one directory.

Uhm, what other Office Suite is there on Linux?

  • Openoffice is discontinued and Libreoffice is the modern Openoffice.
  • There is KDEs Calligra which can do stuff but I see no reason for it.
  • WPSOffice is available as a Flatpak wrapper, the app should not be trusted but it runs on XWayland without problems. But really dont use it.
  • online office suites work perfectly fine through a Browser (Collabora, Onlyoffice, Google cancer, Miscrosoft Cancer)
  • I have no idea of Onlyoffice but isnt that just Libreoffice with the cloud integration? This is really useful, last time I used their version it was just a weird rebranded Libreoffice.

I have no idea why Wayland should cut down your choices. Use XOrg if you want, nobody stopping you, it is simply unmaintained for years pretty much.

There are TWMs for Wayland and they are said to work (have a look at wayblue), I use KDE and tried GNOME and both work. Use any weird old TWM through rootful XWayland if you really want to. This is not waylands problem, X.org is old spaghetticode that nobody wanted to maintain, and there still is no rise in contributions even with all those self-entitled Linux Experts complaining about their weird old nieche Desktop being abandoned.

Nearly (?) all development is done for XWayland, which is normally used in rootless mode, but you can use it rootfull too, and run a complete XOrg Window manager on a minimalist Wayland compositor. Brody Robertson made a video about that.

XWayland is automatically used for all Apps without Wayland support. I never used Gamescope but suppose this is nice, but I dont care about Gaming as I wasted way too much time of my life there. If you want to game, use uBlue Bazzite and call it a day. Its a modern Distro, based on Fedora, using Wayland, made for steamdecks and also PCs.

I never set a single flag for anything and have no idea how Wayland works, but I used it since at least 1½ years.

Wayland has nothing to do with NVIDIA. It was not ready when it “came out” so people where not giving it a chance for obvious reasons. They preferred to use extremely insecure and unmaintained but working Display management.

Now the pressure finally rises, NVIDIA already shipped a lot of updates for Wayland, but in the end it is their fault and you may not want to use hardware from a company that doesnt give a sh*t about FOSS on Linux. I have no idea why people would want to do that? There is literally the high likeliness of backdoors in your damn GPU driver, allowing the green team to see everything you do.

Why use Linux if you entire Graphics are using a proprietary black box?

Wayland is ready. I have no idea of developing Apps, but I suppose just using a good Toolkit is the start. If you are lazy just use Electron, but Qt works just as well cross-platform, if you are fancy use Slint. We can argue if developing apps for Linux is ready.

I think there are bigger problems like good easy IDEs (only GNOME has one) for Linux, or the packaging issue that is fixed by Flathub. Wayland is just a change.

I maintain a repo with a list of recommended, modern software

I have tested a lot of apps, and those are the best. Keep your system secure with modern apps following best practices, using portals, that are Wayland native.

And to be honest, people can just use old Software through XWayland forever. They often dont even need to change.

Projects like Bluerecorder are nice and very alpha on Wayland, here I agree they are struggling to make it work but it works. Using OBS for minimalist screen recording is huge bloat.

permalink
report
parent
reply
3 points
*

A respectable rebuttal. Nicely done. Here are some of my responses.

What did you need to set for KeepassXC? The flathub version and fedora RPM just work.

QT_QPA_PLATFORM=wayland

You can modify flatpak permissions easily in KDE or using Flatseal though, to remove a lot and especially restrict keepassXC to only readwrite one directory.

I prefer my distro’s repos whenever possible. But good to know.

  • Openoffice is discontinued and Libreoffice is the modern Openoffice.

But it works on X. I like using alternatives to the big players in any and all tech spaces. That’s why I use Open Office. That’s why I want an alternative office suite that works on Wayland to actually compete with Libreoffice(that isn’t the online office suites, etc. We appear to be in agreement on that one). But good point, not a Wayland problem. I’ll acquiesce to you on that one.

I have no idea why Wayland should cut down your choices. Use XOrg if you want, nobody stopping you, it is simply unmaintained for years pretty much.

I’m not arguing to use Xorg per se, though I can see my arguments being interpreted that way. I’m arguing that the switch to Wayland is more trouble than it’s worth right now for some people, and to say Wayland is ready for all is disingenuous, and to somehow look down on those who simply want to keep using X is a shitty thing to do.

There are TWMs for Wayland and they are said to work (have a look at wayblue), I use KDE and tried GNOME and both work. Use any weird old TWM through rootful XWayland if you really want to. This is not waylands problem, X.org is old spaghetticode that nobody wanted to maintain, and there still is no rise in contributions even with all those self-entitled Linux Experts complaining about their weird old nieche Desktop being abandoned.

No argument that X is abandoned, no argument it’s spaghetti code. No argument that Wayland is the future. I’m just saying it’s not quite the present either. Diversity within the Linux community is a good thing dude. Customizable work flows are awesome for everybody, that’s one of the things that makes Linux so much better than the alternatives. I can’t wait for Wayland to get to the point where it has that many weird possible workflows going on the way X does right now. That way we can have all the security and no screen tearing you want, with the insane amount of customization options I want.

Personally I want BSPWM and sxhkd on Wayland for the same low RAM cost. River is close, and I’m hoping it gets there, but unless I know c, zig, or rust, I’m not going to be able to customize it to the way I have BSPWM out of the box. Is this Wayland’s problem? Hell no! But if I have all I want on X, why switch?

Nearly (?) all development is done for XWayland, which is normally used in rootless mode, but you can use it rootfull too, and run a complete XOrg Window manager on a minimalist Wayland compositor. Brody Robertson made a video about that.

I love Brodie’s channel, and that was a great episode! That said, the fact that so much backporting has to be done through xwayland is an unfortunate necessity. If everything just works on X, and I still need a translation layer on top of Wayland to use what already just works, then why not just wait until everything just works on Wayland? Or just use both?

I know you’re not saying this, but a lot of the sentiment online seems to be ”stop using X entirely now! Wayland is the future because everybody says so. You use Nvidia? Stop! Your favorite app doesn’t work on Wayland? Just use xwayland!" The sentiment is so emphatic, it fails to acknowledge that some entire workflows have been built up around these older applications where no security breaches were encountered, little to no screen tearing was even noticed, and basically no problems occurred. Why bash on these people with this noise when at the end of the day, we just want to get shit done on our computers efficiently, and if X gets us there quicker, and Wayland doesn’t, then why switch right now? Especially considering the Wayland enthusiasts have to argue so hard to convince me it all just works when it clearly works on YOUR machine, and hasn’t for at least me and also a good number of users? Meanwhile nobody’s arguing that despite X’s flaws…everything pretty much has worked for a while now.

XWayland is automatically used for all Apps without Wayland support. I never used Gamescope but suppose this is nice, but I dont care about Gaming as I wasted way too much time of my life there. If you want to game, use uBlue Bazzite and call it a day. Its a modern Distro, based on Fedora, using Wayland, made for steamdecks and also PCs.

I actually have little to say on the state of Gaming on Wayland. I have played Cyberpunk on Steam with proprietary Nvidia drivers on Wayland and it looks okay. Once Nvidia fixes the stuttering issues that hit in 545, I’ll have no complaints on that. But I only play a single game, so I can’t speak to that too much (others have pointed out in this very chat better insights in this regard).

I never set a single flag for anything and have no idea how Wayland works, but I used it since at least 1½ years.

That’s good dude. I genuinely look forward to the day when this is the norm.

I have no idea why people would want to do that? There is literally the high likeliness of backdoors in your damn GPU driver, allowing the green team to see everything you do.

Are you going to also criticize Linux users who then use any proprietary software? Is your pure FOSS system running GNU boot and Parabola Linux? I’m not going to defend nvidia the company, but their users who want support on Linux shouldn’t be told to just chuck their old cards and go AMD. There are many good reasons why they can’t/won’t do that, and it’s not just gaming or cost. They want CUDA support for AI and also:

Why use Linux if you entire Graphics are using a proprietary black box?

Because I bought one before I knew about the Linux ecosystem and the issues with Nvidia and don’t want to contribute to Ewaste if I can help it. Yes I can afford an AMD GPU, and one day, when my Nvidia GPU craps out, I’ll buy one, but why spend the money, time, and effort to replace a perfectly working GPU solely for Wayland support? You listed some good reasons why, it’s just not enough for me personally and probably for others as well.

Wayland is ready. I have no idea of developing Apps, but I suppose just using a good Toolkit is the start. If you are lazy just use Electron, but Qt works just as well cross-platform, if you are fancy use Slint. We can argue if developing apps for Linux is ready.

I’m sorry, you’re adamant that Wayland is ready, but are willing to argue if developing apps for Linux is ready? This seems counterintuitive. Bur yeah, intuititons are often wrong, care to elucidate on why Wayland is somehow ready but app development might not be?

I think there are bigger problems like good easy IDEs (only GNOME has one) for Linux, or the packaging issue that is fixed by Flathub. Wayland is just a change.

This seems like a Linux problem and not an X or Wayland problem. But hey, the Libreoffice argument I made was based on this same unrelated logic, so I’ll digress.

Again, I’m not arguing that Wayland isn’t the future. What I’m saying is that, even now, it’s not ready yet. It’s closer than ever and there’s obviously a big push to have Wayland everywhere, so it’s coming one way or another.

I maintain a repo with a list of recommended, modern software

Thanks. I’ll check this out later.

Projects like Bluerecorder are nice and very alpha on Wayland, here I agree they are struggling to make it work but it works. Using OBS for minimalist screen recording is huge bloat.

Also will have to check this out, thanks.

permalink
report
parent
reply
2 points
*

it is simply unmaintained for years There are security updates that were pushed out like 3 weeks ago. This is simply a lie.

Now the pressure finally rises, NVIDIA already shipped a lot of updates for Wayland, but in the end it is their fault and you may not want to use hardware from a company that doesnt give a sh*t about FOSS on Linux.

Nvidia had good working support from 2003-2024. From 2003-2014 ATi/AMD GPU support on Linux was hot garbage and at first not even open source, from 2014-2016 it was decidedly inferior, and from 2017 on it was supposedly decent. I say supposedly because I’m still a little paranoid about buying that shit because between 2006-2014 AMD fanboys were just steady continually lying their asses off about AMD cards not being steaming piles of runny shit on Linux. The only people less honest than Nvidia fanboys its a SOBs who have been telling us Wayland was ready for prime time for the last 9 years. Hey it might even be true now but who believes liars?

I like nvidias tooling and features. Gaming on X works well. Screen sharing works well. High DPI works well. Mixed DPI works well. i3wm works well. Everything has continually worked well for 21 years.

permalink
report
parent
reply
2 points

If you want to game, use uBlue Bazzite and call it a day.

The server returned this error: couldnt_find_post. This may be useful for admins and developers to diagnose and fix the error

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

Hint: :q!


Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules
2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of “peasantry” to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
4. No recent reposts
  • Everybody uses Arch btw, can’t quit Vim, and wants to interject for a moment. You can stop now.

Please report posts and comments that break these rules!

Community stats

  • 6.5K

    Monthly active users

  • 1.3K

    Posts

  • 71K

    Comments