>X11 has a bunch of problems that we can't name but they really are there ok also it's just old and old bad new good
>our solution is to force you to use this new protocol that has been in development for over a decade and is nowhere near ready for human use and fixes none of X11's non-existing problems while introducing a wide range of new actual problems that will not be fixed because they're all by design
Why do people continue to fall for Red Hat's retardation?
I hate the antichrist
X11 has a bunch of problems that we can't name but they really are there ok also it's just old and old bad new good
Other urls found in this thread:
gist.github.com
github.com
twitter.com
same thing they did with gnome
for me, it's mate on xorg with runit
>I hate the antichrist
Why?
i hate wayland
i hate libadwaita
i hate gnome
i hate proprietary software worshiping gamers
i hate gimp
i hate electron
I sure do love having to jump through a dozen hoops just to take a fucking screenshot. Thank you wayland, very cool
i would say i hate bloat and include these
> (on my opinion) wayland is not that bad tho, it has sandboxed xorg incase
cut the middleman and just run straight xorg
Wayland is such a fucking circus show of a project it's not even funny anymore.
If it ever matches X11 in functionality, it's going to end up being just as bloated.
Remember, Linux for Niggers uses X11.
By the time it does, Wayland will be as old as xorg was when they started development and they will push for yet another protocol that doesn't work for the sake of being new
xorg is lighter despite having more features. wayland is an absolute fucking scam. if you don't want bloat use the linux console which can do 80% of work already (even gayming)
That's quite likely. Maybe the primary selling point will be that compositor and window manager don't have to be the same process.
Lol who the fuck even cares about Wayland
only the type of faggots that suck gnomes dick and smile after it blows it's aids filled cum load into their mouth would defend let alone wait for this shit
> If it ever matches X11 in functionality, it's going to end up being just as bloated.
It's already more bloated despite the lack of functionality:
X11 Hello World:
gist.github.com
Wayland Hello World:
github.com
I use GNOME and I think that Wayland developers are delusional faggots.
They will lash out at GNOME, ironically, for being the only compositor that implements Wayland to the letter, without all those optional extensions.
Remember when wm4 sperged out against GNOME for not implementing idle_inhibit? Guess what, idle_inhibit is not part of the core Wayland protocol. A standards-compliant Wayland compositor is free not to implement it, GNOME is just exposing how shitty Wayland really is without all the smoke and mirrors.
Fun fact: Wayland does not require GBM over EGLStreams, that's a lie perpetuated by wlroots devs. Nvidia is still a shit company anyway.
I wish that wlroots tripfag came back, it was fun reading his delusions.
The only thing I care about is game performance.
I experienced a higher frame rate using Wayland in a fullscreen application despite not even acting like it (forced triple-buffering).
I have a suspicion that framebuffer compression goes unused when rendering directly to the backbuffer, so maybe that explains why it runs faster. This happened to me on Windows.
The ideal windowing API for linux
Window* OpenWindow(char* title, int x, int y, int width, int height);
Monitor* GetMonitors(int* count);
void SetWindowMonitor(Window* w, int monitorID);
void SetWindowFlags(Window* w, uint32_t flags); // transparency, resizable, decoration etc..
// all decoration config should be system-wide, like a theme
// if a program wants to look special, it should disable decorations
WindowEvent* PopWindowEvent(Window* w);
void CloseWindow(Window* w);
GraphicsContext* GetWindowGraphicsContext(Window* w); // do whatever the fuck you need to do with openGL or Vulkan etc. to fill this context with an image.
// THE END
WindowEvent*
should just be
WindowEvent
What game, GPU, and compositor?
Xonotic, UHD 630, KDE Plasma on Arch.
>X11 has a bunch of problems that we can't name
codebase is unmaintainable
one window can see what you're writing in another window
performance of compositing environment isn't optimal
>writing an app expecting a running display server and a compositor is comparable
where are you retards coming from?