201–210 of 259 posts
Earlier quoted context omitted.
What are your use-cases not addressed by Wayland? The sway compositor has been standardizing protocols for screenshots, screen recording/streaming, composable desktop components and so on.
Just wait until everyone else creates their own standard protocols.
Wayland was designed to solve a very specific set of use cases and nothing more. The number of times I have read "wayland doesn't do that" or "that's not wayland's job" or "wayland is just the compositor" are telling. Of course a stack that is compositor + windowing toolkits is going to miss countless mission critical use cases in countless workflows, not to mention that it is an even further regression from composab…
What are your use-cases not addressed by Wayland? The sway compositor has been standardizing protocols for screenshots, screen recording/streaming, composable desktop components and so on.
Earlier quoted context omitted.
X is good enough for majority of the users, even if the architecture is not perfect.
The fact X11, as the "standard" windowing environment for Unix operating systems, was ditched by literally all major Unix operating systems created in the last 20 years like Mac OS X, Android, iOS, etc, tells us that X11 is not good enough. For example here is an Apple developer explaining why X11 wasn't chosen for Mac OS X: https://apple.stackexchange.com/questions/168980/if-os-x-doe... (By "Unix operating system" I…
Conclusion I am not defending X11 architecture, but for a majority the features it has are good enough despite of the architecture and limitations.
Earlier quoted context omitted.
> Right, X11 made it possible to have literally hundreds of window managers written to fit all possible tastes. I've used it since its inception, however it has always kind of sucked. I think it goes to it's basic philosophy: it did not enforce policy. This let it survive a long time. It was whatever people wanted it to be. But because of this flexibility, it never became great. It's like the old Lilly Tomlin skit -…
What has become great? E.g. has NeXT / macOS graphics system become great? (Yes, I dislike macOS for its lack of customizability and being opinionated. It may be great for someone, but not for me.)
Earlier quoted context omitted.
Xorg remoting was poorly designed to accomodate DRI/DRM, video card acceleration and had adequate performance to only display primitives on screen. Thats the reasons of poor Xorg remoting adoption. I dont remember seeing anyone in this decade using it - it hands down lost to vnc/nx and rdp.
> it hands down lost to vnc/nx and rdp. Those solutions don't do what X remote desktop does, though. Namely, those let you share a desktop rather than providing independent remote desktops.
Earlier quoted context omitted.
Photoshop pretty much got it right a couple decades or so ago, and they've just been porting it, smearing on new lipstick, and figuring out how to make more money with it ever since.
I would argue that this is true of most of Microsoft Office as well. When did they really add a new feature to PowerPoint that you had to have? And it's no surprise both Adobe and Microsoft have pushed people towards a subscription model for this software: Nobody in their right mind would pay for upgrades otherwise. Arguably Office you need every ten years to ensure you have security updates because of the amount of…
Earlier quoted context omitted.
If you click and drag a window around in xorg, does the window stick perfectly to the cursor or is there still noticeable lag?
I use a tiling wm (i3), so I can't exactly drag windows around, but I can drag-and-resize them. In my case, there is no lag. However, there is a tiny amount of stuttering since I don't use a compositor, but I can live with that.
Sure you can. Just pop the widow into floating mode; I think the default is meta-space.
Wayland was designed to solve a very specific set of use cases and nothing more. The number of times I have read "wayland doesn't do that" or "that's not wayland's job" or "wayland is just the compositor" are telling. Of course a stack that is compositor + windowing toolkits is going to miss countless mission critical use cases in countless workflows, not to mention that it is an even further regression from composab…
What are your use-cases not addressed by Wayland? The sway compositor has been standardizing protocols for screenshots, screen recording/streaming, composable desktop components and so on.
Last time (which was when Fedora first shipped it by default) I looked at Wayland, it took me less than an hour to run into several showstopper issues and move right back. The ones I remember include being incompatible with the proprietary Nvidia drivers (and no plan to ever fix that), huge input lag (apparently stemming from the, um, "interesting" idea to make the compositor responsible for all input) and lots of ra…
> incompatible with the proprietary Nvidia drivers (and no plan to ever fix that) I've heard that Nvidia is fixing this in KDE Plasma and maybe Gnome too. (Fuck proprietary drivers though, and fuck Nvidia.) > huge input lag that's odd. Gnome's compositor is not the fastest, but it generally works okay for many many people. > the reasons one should consider a switch nowadays - No screen tearing ever, every frame is pe…
I'm sorry, are you saying that drivers now match specific DEs? That's a sufficiently hideous layering violation to make me automatically dislike Wayland, iff true.
Earlier quoted context omitted.
I've been reading through the Vulkan spec, which is in way similar in that OpenGL has been extended since its introduction in 1992 with more and more features to support new graphics capabilities as they evolved. I've seen Vulkan called the successor to OpenGL, but reading the spec it seems more like the end game for raster graphics card programming. OpenGL 4.0 was released in 2010, and since then changes have been i…
Photoshop pretty much got it right a couple decades or so ago, and they've just been porting it, smearing on new lipstick, and figuring out how to make more money with it ever since.
Not to Linux :(