41–50 of 102 posts
Earlier quoted context omitted.
We're in 2024Q3, things have improved. Nvidia helped out. (X)Wayland/KDE/Qt/GNOME bugs were fixed. Apart from that, use X11 as long as you wish! I'm just glad we can finally improve the open source desktop-environment infrastructure to match those of Windows and macOS: we've been stuck for too long.
X11 was and still is superior to wayland
as long as i need to run nvidia with multiple monitors, i'll hang on to x11.
Is there an issue with Wayland for your setup? I run Gnome + Wayland on Fedora, with two monitors with different sizes and different refresh rates - eerything seems to run pretty fine, including gaming?
Earlier quoted context omitted.
Ya let's integrate gpu-accelerated emoji generation into unicode and require it everwhere, we can call it UTF-8B and standardize on 8GiB per character until that turns out not to be enough.
UTF-8 is innocent here, it's just a (very clever and useful) encoding of Unicode. The problem is adding junk codepoints based on current political ideology, not how they are encoded.
Fun project, thanks for sharing! On Gnome there is the "Characters" application which is pretty handy. I do want to make a few improvement to search, but otherwise it's pretty good. You copy the unicode character to the clipboard and can then paste it wherever you need. If you run Gnome it's probably already installed. If not: https://gitlab.gnome.org/GNOME/gnome-characters
Earlier quoted context omitted.
Ya let's integrate gpu-accelerated emoji generation into unicode and require it everwhere, we can call it UTF-8B and standardize on 8GiB per character until that turns out not to be enough.
UTF-8 is innocent here, it's just a (very clever and useful) encoding of Unicode. The problem is adding junk codepoints based on current political ideology, not how they are encoded.
In case someone wonders what's "special" about it: user perspective: As far as I know, it's the only tool offering somewhat reliable emoji input using faked X11 keyboard events. "x11-emoji-picker" comes close, but delegates faking events to "xdotool", with weird consequences like having to restart it to direct emojis to a different window ;) hacker perspective: It directly integrates xcb in a different event loop (he…
why not use xcompose?
Earlier quoted context omitted.
why not use xcompose?
Not sure you really mean the compose mechanism provided by Xlib (and xkbcommon etc ...)? If so, this wouldn't work for all these emojis that are represented by grapheme clusters, ZWJ-sequences or are just "qualified". The result of a compose sequence is limited to a single "key symbol", which can only encode a single unicode codepoint. Even for those emojis consisting of a singe codepoint, it would really miss the po…
but i agree that compose is not a great user experience
Unicode sucks. There is a glyph for a hammer, for a screwdriver, but not a soldering iron. During COVID, people were using a golf club as a substitute for a cotton swab. We now have generative AI that can make any desired emoticon you can dream of, except you can't use it because of Unicode.
[1] Consider if your vector image representing a soldering iron is someone’s IP, and they rescind licensing for use/redistribution of it. Poof goes all the (legal) copies of your emoji, leaving future historians scratching their heads about what was supposed to be there in the text, and what meaning it contributed. (A concrete case of this actually happening — though not with vector images, but rather stock sound effects: https://roblox.fandom.com/wiki/Roblox_death_sound)
Earlier quoted context omitted.
We're in 2024Q3, things have improved. Nvidia helped out. (X)Wayland/KDE/Qt/GNOME bugs were fixed. Apart from that, use X11 as long as you wish! I'm just glad we can finally improve the open source desktop-environment infrastructure to match those of Windows and macOS: we've been stuck for too long.
X11 was and still is superior to wayland
"was" sure. "still is" it depends on your use case.
for me Wayland overtook X11 as superior in the last year.