Earlier quoted context omitted.
If it's preventing your users to switch to your platform, it's your problem too...
Microsoft releasing worse implementation for competing system? How surprising. /s The linux team client seems to be completely unmaintained and might be thrown away soon. If you need to use teams, use it in a browser.
X12: Requirements for a successor to the X11 protocol (2013)
301–310 of 318 posts
Re: X12: Requirements for a successor to the X11 protocol (2013)
#302Earlier quoted context omitted.
> Graphics are actually a relatively small part of a graphical user interface, something Wayland is still slow to learn. This I think is a key insight. I talk about this in another post, but I've been working on "porting" parts of Xfce to Wayland, and there are so many things missing in Wayland that have nothing to do with "graphics" that means that Xfce+Wayland will be missing a lot of useful features until/unless W…
This sounds suspiciously like the conversations around "just use OpenGL/Vulkan instead of DirectX". Because DirectX is more than just Direct3D?
Re: X12: Requirements for a successor to the X11 protocol (2013)
#303X is almost 40yo, stable, reliable, difficult to maintain. Wayland is 15yo, barely usable. Any old timers remember 1999 when X was 15? Wayland is like IPv6 of desktops
Anyone who believes that XFree86 was stable in 1999 was apparently running a different XFree86 to me. The sysrq key was mostly useful at the time for using the SAK shortcut to kill all processes on the current terminal, which with luck included your wedged XFree86 which would then get respawned by xdm. I don't miss those times.
Linux is and was awesome, I still recall installing it using boot/root floppy disks, but X was around well before the '386 machine in the corner being used for CD creation was recognized as "Hey, this is actually useful"...
Re: X12: Requirements for a successor to the X11 protocol (2013)
#304X is almost 40yo, stable, reliable, difficult to maintain. Wayland is 15yo, barely usable. Any old timers remember 1999 when X was 15? Wayland is like IPv6 of desktops
Re: X12: Requirements for a successor to the X11 protocol (2013)
#305The discussion about "wayland vs X11" is eerily reminiscent of the discussion of "systemd vs. sysv-init"... Some people apparently really do hate it when things change that they seemingly have no control over Edit: I fully expect to be downvoted into oblivion for this post :-D
The problem is that systemd vs sysv-init is a false dichotomy. Systemd took over a ton of important non-init functionality, like DNS, logging, and interactive sessions. That could be fine if systemd did so in a nice and rock-solid way, but it was unpleasantly bug-ridden for years after being thrust on mainstream distros via a hard Gnome dependency. SysV-init sucks in many ways, it's well known, and I can personally a…
Re: X12: Requirements for a successor to the X11 protocol (2013)
#306Earlier quoted context omitted.
This sounds suspiciously like the conversations around "just use OpenGL/Vulkan instead of DirectX". Because DirectX is more than just Direct3D?
Used to be; meanwhile, DirectDraw/DirectInput/DirectSound/DirectPlay/etc have been dead for quite a while.
Although all the other Direct services are dead, have they not been replaced with new versions?
Re: X12: Requirements for a successor to the X11 protocol (2013)
#307Earlier quoted context omitted.
I don't dispute that. My claim was, that both options you mention are broken, and for that one "working", "limping" would be a better term. Certainly not something you would architect a display system around.
I have been using linux for over 20 years and reliable hardware acceleration has always been more "miss" than "hit." This goes all the way back to having to disable hardware cursors on my very first linux setup. I hear the amdgpu driver is pretty solid, and the i915 driver I use on my laptop is great. Nvidia is just a mess (nouveau and the nvidia binary drivers are differently buggy) and the radeon driver is complete…
Not implemented functionality - sure. I've never got TV out running on Radeon 7500 (RV200) during early 2000s, for example. But basic functionality (today), like freezing texture mapping on a hardware, that has 3d driver implemented and that driver comes with distro, no. But then again, maybe I was lucky in my picks.
Re: X12: Requirements for a successor to the X11 protocol (2013)
#308Earlier quoted context omitted.
Used to be; meanwhile, DirectDraw/DirectInput/DirectSound/DirectPlay/etc have been dead for quite a while.
I don't do Windows development, but I remember that used to be the rebuttal from game devs that Linux missed the point about all the ease of use features that Microsoft provided. Although all the other Direct services are dead, have they not been replaced with new versions?
They were replaced not by new versions, but by new or even existing libraries/subsystems, that are not marketed as Direct anything anymore. Just like alsa or pulse are not marketed as SDL or Open anything either.
Re: X12: Requirements for a successor to the X11 protocol (2013)
#309Earlier quoted context omitted.
Wayland is the default on RHEL since 2019. Wayland is the default on Centos since 2019. Wayland is the default on Ubuntu and Debian since 2022. In Arch, Wayland is the default for GNOME installs. Wayland is far from "barely usable" And yes, I remember 1999. X was a pain to get working properly with many graphics cards. Some things never change...
Have you ever tried sharing your screen? Do your organization uses Microsoft Teams? It is barely usable for quite some people.
https://packages.microsoft.com/repos/ms-teams/pool/main/t/te...
Re: X12: Requirements for a successor to the X11 protocol (2013)
#310Earlier quoted context omitted.
If it's preventing your users to switch to your platform, it's your problem too...
Microsoft releasing worse implementation for competing system? How surprising. /s The linux team client seems to be completely unmaintained and might be thrown away soon. If you need to use teams, use it in a browser.