The solution is forced only by the fact that it's the solution and not a ugly workaround.Wayland provide "forced solution" for that problem, that does not mean X can't have some solution to prevent tearing .
Pixel perfect screen, can you image anything more terrible? Even now there are smartphone with an equal amount of RAM compared to my laptop, so the downside seems to be simple irrelevant.And which known dowsides that solution has?
Yeah, and a kernel force users to have some hardware, the absence of the kernel does notWayland force users to use compositor, xserver does not .
I have no idea what you mean here.Some people have issues looking at anything which is composited, so Wayland is not something which magically "God send to as" .
An image can be composed by pixel coming from different source or as a part of a single source, but at the end it's an image sent to the screen. Y frame for each second, but still they are images sent to the screen. What kind of differences the people see (or think to see) between a composited screen vs a not composited one?
The problem is not if it is software or an alien object, the problem is if it is good or not for its tasks.It is just software (althorough with good ideas), but nowhere near finished nor so widely supported and it is nowhere near robustness of X, which is this article all about .
About the "finished" and "supported" points, the things can change pretty much in just 6 months, we will see.
About the robustness, and I add the security, a slim protocol is better to fix and maintain rather than a giant mess like X.
let me clear some details that people got very wrong here:
1.) Wayland is tear free by design by default but can be overridden by the client but in X11 server is factually impossible without breaking the X11 protocol (said by Xorg developers not me)
2.) you can test today with MPV(best wayland support video player) and weston, no matter what you do it won't tear regardless the video
3.) composite don't mean UI effects or anything related to it, it just a nice after effect because you can use OpenGL to draw instead of the horrid XRender API for nice effects(in X11 case)
A global compositor(weston, mutter, kwin, etc) is a system that control how the buffered surfaces go over the screen, for example:
* hey compositor put as screen root background this PNG file and on top of that image remember to show the buffer of application MyApp that it rendered correctly, ohh and before i forget buffer ID=XXXXXX which belong to MyApp2 is requesting to be shown without changes at position X,Y and wait wait i received an input event type mouse click on the area of buffer ID=YYYYYY please proxy it to MyWidget1 and wait for response and go on.
A Local compositor is an internal application system designed by the application developer to control the render process(this one is optional), for example if you are developing a tetris like game you can use a local compositor to do no-op rendering, just upload all your textures once and design a compositor that reference the memory location of each texture and just move them inside the GPU memory instead of actually re upload and redraw the same objects each frame with regular OpenGL (lot harder than it sounds, just as an example)
Now all that eye candy you love or hate was never in the examples because is not part of the compositing process but thanks to the compositing process you can apply post processing the actual buffers before the frame are swapped. To make it easy to imagine lets say in composite each window is like a photoshop layer that you can edit without modifying the layer below(aka you can add effects and stuff without damage the whole image) and non composite is like draw pixels with paint and swap to screen is like flatten an photoshop multilayer into a JPG
It is "lucky" of course for driver developers because most of Windows users use one wm (most of them don't even know something other can exist ) so drivers can easely prevent most of the tipical cases, but of course not all .
Are you implying that Windows is not developed by a whole team? What is it then, a one man show?that is why you need a full team to develop the whole os - then you can do anything you want, you can integrate things to work perfectly, like windows
Man, the quality of your trolling gets worse over time, as it seems. I guess you are only here because it is not good enough anymore for other forums. Somehow Phoronix seems to attract low quality trolls. Maybe the lack of moderation?
Last edited by Vim_User; 07-08-2014 at 12:24 PM.
I came to think Windows trolls coming here to broke Desktop Linux just because with ideas with that "magical" Wayland which have tear-free by design, but if it cause more jitter (and i can bet that is the case) no gaming users will like that . Now is there solution for that - tear-free together with jitter-free So long, viva la X .
I have the compositor enabled in my XFCE installation yet all effects disabled, because I don't want those. (The only thing that "makes use" of compositing is the terminal background being alpha-blended ...)
Likewise you can create a Wayland compositor without wobbly windows or window shadows.
Composition in X for me is anything which use AIGLX.
Disable that in xorg.conf and than see what effects you can get .
Last edited by dungeon; 07-08-2014 at 01:35 PM.
And, as was already said, compositing doesn't mean effects! It makes effects possible, but that doesn't mean you *have* to have wobbly windows. Compositing simply means that stuff is redirected offscreen and is then assembled by the compositor for display. The compositor can apply transformations during this process, which is how you get effects, but that doesn't mean it must.