The last I heard, Wayland doesn't support remote rendering and it's considered out of scope. This is a critical feature for me, which leads me to hope the answer is "never."
try using firefox over X forwarding in 2022.
I've also seen it work fine with 100mbit speeds. But again, I'm not going to make the claim that X-forwarding is the be-all and end-all of remote display solutions; I use mostly RDP and VNC when I'm on the Internet. I never said that X-forwarding is the best remoting solution in all scenarios. You're the one making the argument that everyone who doesn't do things your way is doing it wrong, because you don't seem to understand that other people have radically different use cases than what you're used to. And the flexibility of X11 means that it supports those use cases and others out of the box...and Wayland does not.
In fact, the only thing I've seen going for it is that a) people don't want to maintain X11 and b) it addresses vague security issues like applications resetting your display settings that almost no-one ever had a problem with. It's not a mystery to me why people complain. You're telling people that they're wrong for using their computers the way they've been using them for decades, and if they only change their workflow and environment (which they may have no control over) then they will be compliant with what's new and happening. I'm not here to defend X11, I have no great love for it, but it's bizarre to be told not wanting major feature regressions is wrong.
I have not had a problem with any application thus far.
I don't. I deal with many thousands of Linux servers. Batteries-included languages and X forwarded are my bread and butter. Losing the latter would make my job much, much worse. Of course, it would be nice to install random packages, but I can't.
> The only reason it seems anyone would even consider using it is because ssh has built-in support for it, or if you only use a handful of small Xaw3d or Motif applications with no graphics or bitmaps.
This is absolutely absurd and a completely ridiculous exaggeration approaching slander. I use perfectly normal, modern applications with X forwarding every day with zero issue, including web browsers (Firefox), image editors (GIMP), file managers (Dolphin), IDEs (Eclipse), various developer tools (MySQL Workbench) etc.
Frankly, a comment like this is shocking because it's plainly untrue.
> The only reason it seems anyone would even consider using it is because ssh has built-in support for it
This is a tremendously bigger upside than you seem to be giving credit for.
I'm going to just say it in this comment, because HN rate-limiting is hitting me, but none of the solutions you mentioned meet the criteria I described in the other post.
For me, X11 forwarding:
- works out of the box, no config needed
- works on an application level rather than desktops; this is key
- doesn't require anything network-wise but SSH
- doesn't require me to modify servers in tightly controlled environments
These are all mandatory requirements for me.