...they started over, and then they made a completely functional thing that could actually be improved, that you don't like because... waypipe wasn't implemented first?
"linux does not need games anyway, games are for children" says the man crying about a compatibility layer that according to them should not affect them at all.
You are a very confident person who knows very little about what they're talking about. All the people who do know what they're talking about, as evidenced by the fact that they used to MAINTAIN X11, say you're wrong. Good luck convincing them. Good luck convincing anybody, why don't you maintain X11?
It's important to your specific niche usecase, maybe.
I've never needed to use network transparency, I don't know anyone who has ever needed to use network transparency, and even if I did, i'd use waypipe... so...?
Don't you think that if NOBODY understands it and is willing to support it... maybe it's just fucked?
There are no actual issues going on with wayland development, you're just being a crybaby about network transparency. It's not even not there, you just don't like that it was implemented later...
No, it should be an afterthought. It's not important at all, it's a niche weird use case. I care way more about having a functional desktop and everything else. I'm very glad it was treated as an afterthought, because I care more about literally every other feature.
Tell me why it being an afterthought matters exactly?
The spec was the problem, it was awful, again, none of the devs agree with you. The people who deal with this and are experienced with it ALLL chose to move to Wayland development.
This exact thing happened with x11, you clearly have not researched the history of this.
Your app will work across all of Wayland, the reason this happened is because wlroots came out after gnome and kde made their implementations... kde and wlroots have worked together to the point where kde's compositor is almost identical to wlroots. The only apps I'm aware of that don't work are display managers but that's only because the protocol for that hasn't been stabilized yet.
Unfortunately your usecase is rare, so, there's little motivation to fix it. This isn't because everyone else "just plays around" with their computers, it's that very few people do what you do, and so it isn't considered the most important usecase, and devs care about more important things. Furthermore there's NO DOWNSIDE whatsoever to making it an add-on. This can all be worked on later, it being an add-on won't impede any progress, in fact, it'll make it EASIER to make progress, because the core protocol will be rather solid in foundation.
More work to implement a WM without using something like wlroots? That's a fundamentally flawed argument, you seem to believe there is no X protocol, when in fact, X11 is just an implementation of the X protocol, just like wlroots is an implementation of the wayland protocol.
Have you ever tried implementing the X protocol without X11? Good luck. There's no other implementations because creating one is awful. Wlroots solved the same problem as X11 did, actually implementing the protocol in a way that other projects can make their own WM's/whatnot easily.
wlroots IS equivalent to X11, wayland is equivalent to the X protocol. Nobody has reimplemented the X protocol.
wlroots is an implementation, just like x11, so, yes, that is how it works on the x.org side of things.
It's because he does things that sound cool to him and doesn't handle any of the engineering when it's too complicated and thus leaves all power to actual professionals
SpaceX does fine because he's minimally involved, as does neuralink. Tesla he's ruined through his involvement but only barely (the stupid touch-based yoke and no lidar, for example).
Communist @ Communist @lemmy.ml Posts 8Comments 335Joined 6 yr. ago
No, it was just a neat little extra feature.
It's also a feature that exists in wayland.