Announcement
Collapse
No announcement yet.
The Process For Eventually Releasing X.Org Server 1.21
Collapse
X
-
Why change X in compatibility-breaking ways, now of all times? Just by the lack of enthusiasm releasing 11.21 we can tell that X is destined for being a compatibility solution. And little else.
-
Guest repliedOriginally posted by NateHubbard View Post
That's a ridiculous statement. At best Microsoft only ignored it, just like everyone else did. It died entirely on its own.
Leave a comment:
-
Originally posted by tildearrow View PostSometimes I really need to know when is VBlank occurring because Mesa has a bugged VSync behavior. Time to put up my demonstration GIF again:
Leave a comment:
-
Originally posted by nanonyme View PostNow I'm really curious. I don't want to GLX to go away either but why would you not want to have buffer swapping with sync to VBlank?
Leave a comment:
-
Originally posted by Weasel View PostNope it would be a total bullshit move but not surprising coming from you.
Let's see, to add more effort, drop it and then have users chroot instead of... having it just work because it's not dropped. I wonder which option is more attractive.
Pure direct xlib has not existed for quite some time. Its no different to how Microsoft ships stuff with windows and turns it into a optional run-time package that you have to install.
Leave a comment:
-
Originally posted by oiaohm View PostX11 protocol defines backwards compadiblity. Dropping xlib out of systems by default could be a good thing.
We have flatpak and snap and chroot so old applications needing Xlib could be bundled up with a runtime.
Someways kicking xlib out and leaving xcb in by default would be a very good thing.
Let's see, to add more effort, drop it and then have users chroot instead of... having it just work because it's not dropped. I wonder which option is more attractive.
Leave a comment:
-
Pardon major rework. Prior Answers are after >
Drop DRI1 and DRI2?
> What about old hardware?
DRI2 there are pure DRI2 drivers left. All DRI2 drivers have in fact migrated to DRI3.
The problem with dropping DRI1/DRI2 is not old hardware. Its the NVIDIA closed source driver. It will break the NVIDIA closed source driver because they are using deprecated calls. Really its over due for this.
Drop all drivers except xf86-video-modesetting?
> What about old hardware?
Old hardware since the disappear of UMS drivers is support by modesetting how.
Create a GLAMOR built a top of Vulkan instead of OpenGL?
> Vulkamor
Revise DRI3 to v3.3? (with what?)
>OK...?
Drop Xlib in favor of XCB (never going to happen)
>Please don't. I know you like breaking compatibility, but this is exactly why Windows has been a success (in many cases it is backwards compatible).
We have flatpak and snap and chroot so old applications needing Xlib could be bundled up with a runtime.
Someways kicking xlib out and leaving xcb in by default would be a very good thing.
AR/VR stuff? A new XRandR version?
> Probably. What would that new RandR version bring though?
Drop any acceleration architectures? Is EXA, SNA, UXA, KAA, XAA all really needed? We now have GLAMOR!
>I repeat: What about old hardware?!
Like work should be put in to finish off the merge of KAA and XAA into EXA. That would kill off 2.
SNA by intel is on by default. UXA is intel old superseded. SNA is meant to support all hardware that UXA did if it does not its a bug.
So out of the list really only 3 should exist. EXA, SNA, GLAMOR. Using the others is really work around to a bug in EXA or SNA.
A build flag to build a reduced, minimal X build only suitable for usage through XWayland?
Is Panoramix/Xinerama, COMPOSITE, DamageExt, GLX, DBE, and framebuffer still needed?
Is Xinput and xkbd still needed with libinput?
A build flag to build a reduced, minimal X build only suitable for usage through XWayland?
>Would be cool, but somebody should re-engineer the whole XWayland architecture anyway.
Is Panoramix/Xinerama, COMPOSITE, DamageExt, GLX, DBE, and framebuffer still needed?
>Yes, many of these still needed! Are you crazy?!:
>Composite is necessary to have a compositor.
>Damage is necessary for battery/power savings as it allows telling a compositor only to render a small portion of the screen
GLX? Look. Why would you want to remove something 95% of applications still use?! (furthermore, please tell me how can I wait for VBlank without swapping buffers in EGL)
Is Xinput and xkbd still needed with libinput?
>Are you serious once again? libinput is a backend to XInput/XKB. Furthermore, once again, what about old hardware?
Almost all the old drivers hardware support has been moved into libinput.
The effected hardware list is insanely small if you remove the GLX one out that list and ingnore the Nvidia closed source driver death.
If Intel graphics card turns out to be high end then doing this level of extreme will be more possible.
Leave a comment:
-
Originally posted by smitty3268 View Post
Getting rid of X entirely would do a better job of that if that's what distros are interested in.
Leave a comment:
-
Originally posted by nanonyme View PostUhm, the entire protocol was just redesigned from scratch as HTTP2 a short while ago. Bad analogy.
In fact, you can track it's history back through SPDY which was initially announced right around the same time that Wayland was. You could very roughly compare http1 and x11 dates too, if you wanted to extend things even further.
All of which is ignoring the fact that my post was obviously sarcastic and not meant to be thought too deeply about.Last edited by smitty3268; 16 May 2019, 03:16 AM.
- Likes 1
Leave a comment:
Leave a comment: