EVERYTHING CRASHES WAYLAND

EVERYTHING CRASHES WAYLAND
HOW IS THIS ACCEPTABLE

THE DEATH OF XORG IS REAL

Attached: proxy.duckduckgo.com.jpg (474x474, 28K)

Other urls found in this thread:

github.com/swaywm/wlroots/issues/655#issuecomment-511098029
old.reddit.com/user/_diablo2_
old.reddit.com/user/CuBeRJAN3
news.ycombinator.com/threads?id=sprash
blogs.gnome.org/uraeus/2019/06/24/on-the-road-to-fedora-workstation-31/
gitlab.freedesktop.org/wayland/wayland-protocols
gitlab.freedesktop.org/wayland/wayland
twitter.com/SFWRedditImages

works on my machineā„¢

wayland can't crash

Attached: Screenshot from 2019-07-16 16-28-22.png (1024x815, 43K)

>github.com/swaywm/wlroots/issues/655#issuecomment-511098029
can any1 explain this 4me
thanks 4channel

I'm more worried about Wayland being thought as a good replacement when it has severe latency issues and forces vsync.
>b-b-but user, latency isnt a problem!
No you innocent glow in the light, some of the most-used DEs/WMs on Linux have latency so high they sometimes manage to do worse than windows 10. Some software/games already have latency up through the roof so why shoot yourself in the foot with another 50ms?

Attached: linusface.png (233x242, 102K)

Oh look it's this FUD again. Wayland is a protocol. It doesn't have any latency or vsync. Both those things are up to your compositor. Report your bugs in mutter, kwin, sway, or whatever.

worst case scenario it works like windows where fullscreen programs and games bypass the compositor

waylands a protocol

Sure but what about xwayland?
KDE doesn't do fullscreen unredirection anymore. And it seems to be the same for GNOME 3.

Read the linked collabora post, when the compositor starts drawing immediately after a page flip the clients don't have time to get their updates in before the entire frame is composited. The solution is to delay compositing until the middle of the frame so the applications have time to redraw.

>has severe latency issues
False.
With wayland it's possible to achieve 0 frames of latency in your own applications.
And that is simply impossible on windows.

And with other people's applications? In games that don't support wayland? It's the limitating factor.

Fud again? yummy
These are the kind of 4channedditors that you're arguing with
old.reddit.com/user/_diablo2_
old.reddit.com/user/CuBeRJAN3
news.ycombinator.com/threads?id=sprash
They are all on the same discord circlejerking

If your application uses GTK3, Qt5, or SDL2 then it already supports wayland.

The thing is that the "latency issues" are not a fault of the protocol itself.
Legacy programs require workarounds. That is the issue of the compatibility layer.

oh no, i've been found!

wtf i love wayland now

wayland's a massive meme. it's fucking garbage. half the shit doesn't work and the other half works poorly.

You're partially right, for now. Most of the development (i.e. not protocol work) started ~4 years ago.
Now that the biggest maintainer of X dot ORG has announced to the world that they should work towards Wayland support everything will progress much faster.
Keep a tab on related projects and technologies that Wayland enables: better sandboxing, PipeWire, salted gamer tears, improved developer experience (remember kids: most toolkits like Qt and GTK were already ported, and Firefox and Chromium are on the way).
---
---
---_ This post will earn you: 67 cents. Don't forget to delete this line!

>Now that the biggest maintainer of X dot ORG has announced to the world that they should work towards Wayland support everything will progress much faster.
heh? where are you getting this from bro? haven't heard a thing about this...

WAYNNIGGERS BTFO

>blogs.gnome.org/uraeus/2019/06/24/on-the-road-to-fedora-workstation-31/
from uranus himself

XBOX
CRASH WAYLAND FOR ME

OpenBSD doesn't have this problem.

wayland is a kernel

Wayland is a code base, it's not even a spec let alone a standard.

openbsd also doesn't have working drivers or software

>gitlab.freedesktop.org/wayland/wayland-protocols
>Wayland protocols that add functionality not
available in the Wayland core protocol
>gitlab.freedesktop.org/wayland/wayland
>Core Wayland window system code and protocol

Maybe you pushed the wrong button, retard.

wayland is stored in the balls