271–280 of 318 posts
Earlier quoted context omitted.
> The majority of graphics cards are Nvidia The majority of graphics cards are Intel.
Very few graphics cards are Intel.
Also note, that users that use graphics cards are minority themselves.
Earlier quoted context omitted.
None of Waylands internal functions between a client and compositor are blocking or synchronous to my knowledge. Generally you fire off a message and will later receive an event back from the compositor, which is happening in an event loop. There is an exception, which is the explicitly blockling "roundtrip" function(s), but that is meant for special cases only. Being asynchronous was an design goal for Wayland from…
This isn't that different than X though which also has the fire off a message and receive event back. Very few of the functions actually make you want (even in xlib, which wraps the protocol itself to be a bit easier to use from C, the majority of functions still are async - much to the chagrin of newbies trying to decipher error messages)
Earlier quoted context omitted.
1) no, he complains that X11 has a big core and then extensions. Extensions are fine, but they were unable to kick out parts of the core, because it is the core and something somewhere assumes it is there. So they had to maintain it, despite not being used in practice, except by that little something that nobody can point their fingers at. 2) he talks about obsolete hardware. There's no really a point to support s3 t…
> That graceful degradation is in practice the same, as just using Wayland. Ever tried to use modern X11 app over network? RDP is vastly better experience, (and RDP support is wip in wayland). I do, in fact, use modern X11 apps over the network literally every day. Some are better than others - if the programmer made the effort to actually gracefully degrade it can be a considerably better experience than the ones wh…
RDP does support integration of windows from multiple computers, in a way of RemoteApps. Even if you are running GUI apps inside WSL2 locally, you are using it.
Earlier quoted context omitted.
At our uni, we used DEC and had vxt2000 terminals. It worked fine, just like wayland does today. But it wasn't rock stable, or even remotely secure.
Secure no, lol. But in those days telnet was still the norm. At my college they didn't even have xauth implemented which was loads of fun embarrassing other users with xv and some cool pictures :P Or xblast
Earlier quoted context omitted.
this. the whole "sysv init is so slow because of shell scrips" was a scapegoat. yes bash is relatively slow. and yes, dash is the answer to that problem, not systemd. they who control systemd now control Linux as an OS. not as an API (that's kernel/libc) but as an OS. how you manage it, run it, suspend it, initialize it, turn it off, everything was RH, and now is MS.
RH is s/MS/IBM/, quite literally.
But Microsoft employs Lennart Pöttering, so that might be what the comment meant. Pöttering created systemd and is the main maintainer, even now.
X 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
More like the R6RS of desktops.
EDIT: This comment may age poorly when R7RS Large is complete.
Earlier quoted context omitted.
> That graceful degradation is in practice the same, as just using Wayland. Ever tried to use modern X11 app over network? RDP is vastly better experience, (and RDP support is wip in wayland). I do, in fact, use modern X11 apps over the network literally every day. Some are better than others - if the programmer made the effort to actually gracefully degrade it can be a considerably better experience than the ones wh…
If you don't mind answering, what do you do that uses GUI over network? Not looking to argue or try to claim would work better or anything, just curious what people use it for seriously these days.
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.
Earlier quoted context omitted.
YMMV. When it reaches the level of X11 that "just works for everyone without preconditions" it will become usable in my coordinate system
I remember in the early 2000s still needing to write to a config file to get X to work on my desktops at the time. Was it 30 years old at that time? I've been running Wayland crash free for a few years already, without the need to touch a single config file. Does that mean it reached better usability at least twice as fast compared to X?
Earlier quoted context omitted.
I'm on Arch on my work machine and it started working with pipewire about 3 months ago... no config necessary just works as intended both screen and window. There are some others at work on Ubuntu LTS but that is because Ubuntu is using ancient packages.
Ah, but the reply was about defaults . Do any of those distros ship with Pipewire as the default? If so, I'm sure it hasn't been since 2019 as the original poster claimed.