Egregoros · Phoenix Framework

Post

Remote status

Context

Phantasm (away)

17w

And you thought that the X11 IM is insane. On Wayland the situation is even worse.
http://dorotac.eu/posts/input_method/

At least the XMODIFIERS env seems to be gone and a program can ask the compositor to be the IM instead of X11 going down the path of looking at an env variable and doing nothing when the IM in the env isn't actually available.

lain

@lain@lain.com remote

17w

@phnt
> Wayland is gradually getting the ability to support input methods natively.

wayland is 17 years old by now. what have they been doing all the time?

Phantasm (away)

@phnt@fluffytail.org remote

17w

@lain Rust is also technically two decades old this year. And only became usable in the last few years.

>What have they been doing all the time?
Making worse software in the name of user-friendliness. Also the author of the blog is now moving on from IMs in Wayland after more than 6 years of working on them: http://dorotac.eu/posts/im-finished/

The end result is multiple protocols, spread over multiple compositor implementations, that aren't all compatible with each other.

Compared to XIM, which took probably a year or two to make and with all of its also known issues. But at least it's one standard, one protocol, you can use and it will mostly work.
https://www.x.org/releases/X11R7.6/doc/libX11/specs/XIM/xim.html

:VD15_0::VD15_1::VD15_2::VD15_3::VD15_4::VD15_5::VD15_6::VD15_7:

@VD15@pl.valkyrie.world remote

17w

@phnt @lain So what you're saying is that w*yland is too bloated, slow and old to be viable? Clearly we need a clean break from this seventeen-year-old tech and a new display server for the modern ecosystem ®️

Replying to @VD15@pl.valkyrie.world

@i@declin.eu remote

17w

@VD15 @phnt @lain it's time for https://arcan-fe.com/videos/

Replies

Fetching replies…