this post was submitted on 29 Oct 2023
258 points (95.7% liked)

Linux

48332 readers
476 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

I'm not proposing anything here, I'm curious what you all think of the future.

What is your vision for what you want Linux to be?

I often read about wanting a smooth desktop experience like on MacOS, or having all the hardware and applications supported like Windows, or the convenience of Google products (mail, cloud storage, docs), etc.

A few years ago people were talking about convergence of phone/desktop, i.e. you plug your phone into a big screen and keyboard and it's now your desktop computer. That's one vision. ChromeOS has its "everything is in the cloud" vision. Stallman has his vision where no matter what it is, the most important part is that it's free software.

If you could decide the future of personal computing, what would it be?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

Don’t think that is up to Wayland, but UI toolkits. What specifically do you mean?

a11y requires a large range of features, because of wayland most OSKs are now platform specific, we can't have overlays (we might be able to when the layers protocol lands, but thats a privleged protocol which is kind of up in the air how it's handled) etc. a11y requires an entire ecosystem, you cant just lay it on the tool kits, compositors handle a lot too.

They have documentation on how to do this. If there’s no libraries for this yet, it’s not up to Wayland, but maybe lack of interest.

I've tried this a while ago, it's a bloody joke, not only is it much harder to actually just do it, worse performance, and now I need to manage a bunch of additional crap. the fact that this is actually the reccomended process is a bloody joke, if you want window embedding, just use xwayland.

Wait and see. What I’ve seen discussed seems pretty good.

we shall see

Also, they have to take into account that not every compositor is a floating window manager.

I have absolutely no idea why people keep saying this. weston doesn't support some xdg protocols, and gnome some ext protocols, so why the does this matter? clearly neither xdg nor ext protocols are mandatory, so it has nothing to do with compositors not wanting to implement it.

if it's because tiling managers can't do it, then simply combine both protocols into one, or use both protocols.

[–] [email protected] 1 points 1 year ago

a11y requires a large range of features, because of wayland most OSKs are now platform specific, we can’t have overlays (we might be able to when the layers protocol lands, but thats a privleged protocol which is kind of up in the air how it’s handled) etc. a11y requires an entire ecosystem, you cant just lay it on the tool kits, compositors handle a lot too.

Ah, that makes sense. Tbf I'm not too familiar with it and mainly thought about screen readers and such, where only the toolkit knows what text is displayed since everything afterwards just gets a frame buffer. It would be great to get a portable way to do overlays and feedback like "user has focused a text input control", yeah. How does this work on X11?

I have absolutely no idea why people keep saying this. weston doesn’t support some xdg protocols, and gnome some ext protocols, so why the does this matter? clearly neither xdg nor ext protocols are mandatory, so it has nothing to do with compositors not wanting to implement it.

As far as I know xdg protocols are supposed to be mandatory, ext ones aren't. Weston devs just don't care I suppose. (Though I can't actually verify this so correct me if I'm wrong. I just know that getting a protocol included into xdg is a lot harder.)