HNHacker News
TopNewBestAskShowJobs

QUrprUd1nCeicw

137 karma · joined January 6, 2023

submissionscomments
QUrprUd1nCeicw··on Revisiting KDE
There's nothing vile about that, it's normal development practice. If you decide to make a code editor you're not making an app for artists, you're making an app for developers. That's a conscious choice you make when you sat down and said "I'm going to make a code editor today." Unless you think it's stereotyping to consider that people have different skills and professions?

Just think a little bit more about this in the context of your example. A user who isn't a Linux enthusiast or sysadmin isn't going to know anything about what /usr/share or /var/lib, etc is supposed to be. And a user who knows everything about that isn't going to need a fancy file manager to perform sysadmin tasks on those folders! They know how to do everything from the command line already.

QUrprUd1nCeicw··on Revisiting KDE
It's not dumbed-down to make apps that are focused around performing a specific task and making them easy to use. That's literally the entire purpose of designing apps. There's nothing else to it. iPhone and Android didn't invent that either, I think most people would agree that not every app needs to be Emacs.
QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
X11 APIs have no security and they don't work in Wayland. Either one of those reasons is enough to avoid using them.

Aside from that, it's the slowest and worst possible option in X11 because it copies the pixels into the socket. To handle large images you want to at least use MIT-SHM. XGetImage should only be used as a fallback. Or better, just don't use X11 APIs at all.

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
I think you're missing that authors of tiling window managers don't actually want to go back to the X11 way of doing things. They don't want to write a basic window manager or a plugin. That abstraction boundary is bad and it's extremely limited. That's why the X Composite extension was created in the first place. There was a chance to go in the opposite direction with Wayland. People did actually make plugin APIs but they never became standard, few developers wanted to use them. Instead wlroots became popular because it allows a lot more power and flexibility over compositing. The compositing approach is what allows Hyprland to have those nice transparencies and animations. So it's not that I'm trying to be fair to Wayland, I'm actually trying to be fair to X11 compositors. You're skipping that whole step that happened in the mid-2000s when you make your comparison. People wanted to make compositors all along.
QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
That's less and less relevant as GPUs and displays get faster. You might gain a trivial amount of latency in certain cases, with specific apps, at the cost of bringing back stuttering. The normal case is always going to be vsync. If your program is hardware accelerated it's not actually rendering "half frames," it draws the whole frame and the tearing you see is just a result of swapping at the wrong time.

What I mean here is the rendering in clients isn't going to change either way, everything is already built to use vsync. Turning it off is more a matter of how many switches the compositor wants to provide for controlling the throttle. Most compositors should have support for fullscreen unredirect anyway, and that gets you most of the way there.

EDIT: A few years ago this blog by Raph Levien sketched out a way to reduce latency without bringing back tearing, you may want to read it. https://raphlinus.github.io/ui/graphics/2020/09/13/composito...

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
>The Glyphs themselves are rendered only once client side.

That's literally what I just said? The glpyhs get rendered client side and then composited in the server.

>What is your agenda? I truly don't understand.

I don't have an agenda. Do you have to assume everyone has one? Please just take my comments at face-value.

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
It's not a weakness or inflexibility in the Wayland protocol. There's no way to make it work there. They had to rework the way security is done, and that's a much bigger task that touches lots of other parts of the OS. I keep saying this but you're not listening to me. Why?

Yes, if you want to use a secure system then you need to only go through secure APIs. If you cut out security in the name of making a "light" compositor then you just lose the ability to run sandboxed apps correctly, so it's crippling your desktop for no good reason. The XDG portal was built as a secure API to support Flatpak but it doesn't actually need Flatpak. The compositor is what needs to implement it so any sandbox can use it.

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
>Still isn't possible in Debian Stable if I recall correctly.

It depends on the app. Chances are older apps needs to be updated to use the portal.

>There is a small risk that we end up with competing, mutually incompatible ways of taking screenshots on a Linux desktop.

No, there's only one way. Use the XDG screenshot portal. It's not a library, it's a standard API the desktop implements.

>for no particular reason other than they didn't feel like scoping out the original specification a little more practically

There was a reason. They didn't scope it out because they couldn't. Privileged operations need to be implemented using OS-specific security facilities. There's no way to make this work correctly just with Wayland. On Linux it needs a sandbox, and those are very different in scope and design from a window system.

>But hindsight is 20/20 and the wart is now quite obvious.

No, there's no wart. Or rather, if there is a wart, it's on the OS itself and how it does security. Linux didn't have a way to do this kind of sandboxing before, so someone had to invent that too. Efforts to hack sandboxing into X11 (see Qubes OS) have run into these same problems.

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
No, that wasn't a mis-step and it wasn't the wrong policy. Wayland is primarily concerned with taking buffers and telling the GPU to put them on the screen. Buffer sharing between clients is more concerned with the opposite: taking GPU buffers and turning them back into CPU-readable pixels so software can do arbitrary processing on them. Those are two very different concerns.

And because screenshots are a privileged operation, this will always need to go through a back-channel anyway to handle the security aspect. Otherwise you'll end up with a repeat of X11 again where any Wayland client connected to the server can scrape the screen at all times. So for desktop use there's really no reason to ever put it in a Wayland protocol. The design from the beginning was to keep privileged operations (like screenshots and input grabs) out and that still holds true now.

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
>There is no easy way to open a Window and render a string. Period!

Yes, there is. Use a client library. That's what they're for.

>You either need to write it yourself completely (as OP stated) or you can use Gtk/Qt or other heavy weight "client libraries"

This is exactly the same as in X11. Remember Xlib is one of those heavy weight client libraries. The X11 example you showed uses Xlib.

>Look at the code again! If you really think that the code at [1] is in any way a great solution as compared to [2] we are going to disagree.

I don't think either of them are great. I'm saying that's comparing apples to oranges.

>ZERO screenshot apps on X11 use XDG screenshot portal, they all use XGetImage().

They shouldn't. Like most parts of X11, XGetImage is an obsolete API. You don't want to use that in modern clients.

>Mainly because the assumption that a dbus-daemon is always running everywhere is mostly false.

No, dbus is used by basically all modern desktop environments on Linux. If you don't have dbus available you're going to have a lot more problems running normal Linux apps than just dealing with the differences between X11 and Wayland.

>Also XDG screenshot portal is simply not a good solution. It is cumbersome to use, contains tons of edge-cases and pulls a dbus dependency for something that could be solved much simpler with onboard OS-functionality without the need for extra daemons and weird binary protocols

X11 is also one of those weird binary protocols that isn't onboard OS-functionality and has more edge-cases, so according to this XGetImage isn't a good solution either.

>Xft does server-side rendering via XRender.

No, you've got rendering mixed up with compositing. With Xft, the rendering of font data to pixels is still done in the client. XRender, despite the name, is frequently only used to composite surfaces together. That's doing the same thing that Wayland is doing.

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
>Severe over engineering, unstable interfaces, massive boiler plate and huge development overhead is preventing the long tail "at the protocol level".

No, all those can be solved with client libraries. X11 had Xlib and the other client libraries. Those X11 libraries don't make sense in Wayland, but the client libraries that stayed relevant (freetype, cairo, etc) can still be used.

>If you want to add the ability to take screenshots it gets exponentially worse.

No, in both modern X11 or Wayland, you should use the same API for screenshots: the XDG screenshot portal.

>Also the Wayland version is not even capable to render strings.

Sure it is, but you have to use client-side rendering. Client-side rendering is also the norm in X11, since decades ago when Xft was released as another one of those client libraries. That X11 hello world is short because it's using obsolete APIs.

QUrprUd1nCeicw··on Hyprland: A dynamic tiling Wayland compositor
>The problem with "alternative" Wayland compositors is that so much more functionality is pushed into the compositor under the Wayland architecture compared to window managers on X11.

That comparison is a bad one to make. Compared to just a window manager, that's correct. But you have to compare Wayland compositors to X11 compositors and for that it's about the same amount of work. Either one expects you to bring your own rendering because that's the main benefit of writing a compositor.

It also might make sense to compare X11 window managers to compositor plugins. The reason people seem to prefer wlroots is precisely because it offers more power and more control over the just writing a window manager.

QUrprUd1nCeicw··on X Window System Basics (2014)
Wayland already meets all those points. And Plan9 doesn't use either X11 or Wayland. Why don't you take your own advice and switch to Plan9 if Linux is causing you problems? I'll also point out that your statement about being only for developers and power users is untrue. There are plenty of good "newbie" distros like Ubuntu and Mint.
QUrprUd1nCeicw··on X Window System Basics (2014)
I didn't tell you what to say. I asked you nicely. Notice I used the word "please." You can make all the arguments against Wayland you want. Promoting baseless conspiracy theories and verbal abuse calling other people morons doesn't help get your argument across. It weakens your point. You're just hurting people as well as hurting your own argument by making these comments.
QUrprUd1nCeicw··on X Window System Basics (2014)
Global shortcuts and screenshots are already available as standard features. The problem with your thinking is the system needs to be designed to have security by default for it to have an chance of being secure. We know from X11 that "insecure by default" is a mistake that leads to everything breaking later when someone tries to hack it to actually have security. When everything is secure by default, you can still turn off the security checks and allow everything to get access to everything else.
QUrprUd1nCeicw··on X Window System Basics (2014)
Fight who's fire? The Wayland developers are former X11 developers, so you're accusing them of "shilling" against their own project?
QUrprUd1nCeicw··on X Window System Basics (2014)
No, with direct rendering the display server uses the same API as any other process that uses the GPU. The way to fix stuttering is to fix scheduling in the kernel. XGetImage is comparing apples to oranges. That doesn't use the GPU at all, that does a copy into main memory. Pipewire is complicated because it has to handle format negotiation and conversion and audio support and a lot of other things that make sense for generically transferring video between processes but are outside the scope of the display server.

Can you please knock off the conspiracy theories and flames? What are you hoping to accomplish by hurting people like this on the internet?

QUrprUd1nCeicw··on X Window System Basics (2014)
>I suspect that if the Wayland developers simply dropped maintenance of Xorg completely that a community would step up and carry Xorg forward

I don't. That community was sorely needed several years ago, but failed to show up.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Then maybe some of those project maintainers should start a DE, and see first-hand how it's really difficult and requires making a lot of tough decisions that don't apply to other projects?
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Did you get something mixed up? I was saying there were provable facts.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>but given that it's a subjective technical decision

No, there's nothing subjective about it. The fact is, doing things the way they suggested won't fix anything. That's a fact of the code as it's written. They could change the code to fix it, but then they'd be breaking backwards compatibility. These are the objective facts.

>if your ethical framework is "Gnome is all volunteers they can do what they want"

That's not an ethical framework. It's a functional description of the way that open source projects work, by necessity. How do you propose volunteers make anything work if they're forced to program in every idea from every user, including all the impossible and nonsensical ideas? Or what if one user wants to expand a feature but another user wants to remove the same feature, what do they do?

>Yes, I concede that they are free to do whatever they want, but that doesn't free them from criticism.

Neither does it free the SDL developers from criticism from the GNOME developers, or from anyone else. It also doesn't free either me or you from criticism for making impossible suggestions.

>Do you think that the choice to not implement XDG-decoration is based on probable facts?

Yes, see above. The code that's currently written is an objective, provable fact. You can go look at the code right now, that's the code that's shipping on users' computers. Any decision they make is restricted by that code, unless they want users to be even more angry about how they broke backwards compatibility. You're getting confused, because the subjective part here is what they do to the code in the future. The code as it currently stands says objectively that your idea won't work without causing other problems.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
No I'm just a user of GNOME who doesn't appreciate seeing the near-constant flames and misinformation from non-users of the software whenever I try to discuss it online in certain places. It's low-quality commenting and it poisons the discussion. You're misinterpreting an aversion to bad discussion as "defensiveness." If you were doing this same thing for KDE I'd be asking you to stop too.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
No. How would that even make sense? If you have no GNOME-related software on your computer at all then it won't affect it.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
No. The preamble to the GPL describes the spirit. Here's some direct quotes from the GPL v2.

https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html

>the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users

>When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish)

>Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software.

And all of those parts are still the same. The "no warranty" here generally (and legally) means you don't get to complain if it doesn't work for you, unless you believe Stallman didn't understand what he meant when he wrote that.

QUrprUd1nCeicw··on X Window System Basics (2014)
Can you please knock off the conspiracy theories? You don't have to bring yourself down to that level. Maybe consider how those things could actually be useful to people who don't use Red Hat?
QUrprUd1nCeicw··on X Window System Basics (2014)
Can you please knock off the conspiracy theories and baseless personal attacks? Why are you doing this? You don't have to bring yourself down to that level.
QUrprUd1nCeicw··on X Window System Basics (2014)
Can you please knock off the conspiracy theories? You don't have to bring yourself down to that level.
QUrprUd1nCeicw··on X Window System Basics (2014)
>The Display protocol is the only sensible place to negotiate access to GPU resources.

No, GPU resources can come from any number of other places. That's literally the purpose of direct rendering. Any applications using GPU compute can produce them without requiring a connection to the display server. There's no reason to put that in Wayland or restrict it to the compositor. There's already a much better protocol for sharing GPU buffers: Pipewire. Dbus is only there to act as the glue between a Wayland compositor and Pipewire.

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
On a modern Linux distro a web browser installed from Flatpak/Snap will be sandboxed in a container. But you need to be using Wayland too (or setup a separate X11 sandbox) because X11 circumvents the container. Example code for it here: https://mjg59.dreamwidth.org/42320.html
QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
Even if you don't need any features in Wayland there are still benefits, it closes some security holes and it fixes some long-standing bugs in X. Of course it also creates some new bugs like your buggy nvidia driver.
← PreviousPage 2 of 4Next →