GTK to remove X11 backend

Network transparency aside, Wayland is OK enough for consumer desktops and appliances but I simply cannot find a decent terminal emulator comparing anywhere close to xterm or rxvt. Either they are ADHD simulators with annoying bloat and gimmicks or they are alpha quality tech demos written by a student in their spare time.

At this point Weston on X11 runs well enough as a Linux compatibility tool. I can't see it progressing from that for a long while though.
 
i was an rxvt user for many years

but got fed up with the in my opinion poor font rendering
and having to use Xresources for the config

so i switched to alacritty a couple of years ago

Code: 
alacritty-0.14.0_2             GPU-accelerated terminal emulator

Code: 
sudo pkg install alacritty

alacritty use toml for its config file, which is nice and easy
great font support, rock solid and super fast

alacritty modus-vivendi-tinted colour scheme to match my emacs config

github.com

freebsd-dotfiles-xps/.config/alacritty/alacritty.toml at master · NapoleonWils0n/freebsd-dotfiles-xps

freebsd dotfiles dell xps 15 2019. Contribute to NapoleonWils0n/freebsd-dotfiles-xps development by creating an account on GitHub.
github.com github.com

20250213_17h53m05s_grim.png
 
kpedersen said:
Network transparency aside, Wayland is OK enough for consumer desktops and appliances but I simply cannot find a decent terminal emulator comparing anywhere close to xterm or rxvt. Either they are ADHD simulators with annoying bloat and gimmicks or they are alpha quality tech demos written by a student in their spare time.

At this point Weston on X11 runs well enough as a Linux compatibility tool. I can't see it progressing from that for a long while though.
Click to expand...

systemd, Wayland, etc.. all badly designed, Red Hat vendor lock-in child projects. When systemDisease subsumed all of important userspace, and GNOME services (forcing all major distros to adopt it); I knew it was over. The IBM acquisition drove the final nail in the coffin for Linux independence.

Hail IBM.
 
Charlie_ said:
I don't agree with T-Aoki.
I'm tired of T-Aoki writing as if this represents the general consensus of Japanese people.
Click to expand...
Of course, it's MY opinion.
But Japanese people talks, writes Japanese, thus, Japanese IM should work sanely. Do you object this?

Ah, of course, Japanese people who don't write Japanese on computers (write codes only!) should not aware of Japanese IMs.
 
Charlie_ said:
I don't agree with T-Aoki.
I'm tired of T-Aoki writing as if this represents the general consensus of Japanese people.
Click to expand...
Since FreeBSD is quite niche, ultimately T-Aoki provides a good example of someone who isn't happy with its current state that shouldn't be ignored.

That said, many haven't been happy with Xorg in the early decades either (xorg config has traditionally been fiddly).
 
Does anyone using Wayland have a 1000Hz+ mouse? For 8+ years and today GNOME 47 I can still reproduce a floaty cursor and inconsistent movement with high CPU/GPU load, whereas my mouse tracks perfect and consistent GNOME 47 Xorg and Windows. I had a few Corsair HARPOON RGB Pro and non-Pro mice at 1000Hz ($30 off the shelf at Walmart), and an Attack Shark R6 1K-8K.

I've reproduced it with those mice Fedora/Ubuntu/openSUSE with GNOME and Plasma 6, know it was particularly bad prior to GNOME 42, but don't quite get how it's still like this today while Wayland is apparently getting HDR support?
 
T-Aoki write 'NOT AT ALL'.
The extreme claim that something cannot be used at all just because something that should work does not work is not acceptable.
Some people use commercial software(Wnn) to input Japanese, but only use it from Emacs.
For example, like this person
There are also people on Japanese message boards who use the commercial ATOK with wime(use wine), but only use it from emacs.
I don't want to be involved with people who bring up Japanese people who don't write in Japanese in order to refute their points.
I'm not like him and I don't want to be thought of as the same.
 
Charlie_ said:
T-Aoki write 'NOT AT ALL'.
Click to expand...
Imagine the situation that anyone need to write Japanese emails to others that don't understand other than Japanese multiple times everyday. In this situation, if you cannot use Japanese IM, is it usable as the daily driver? No. Not at all usable as the daily driver.

And I've also wrote "It depends" at #30. Anyone who don't need to input Japanese is not affected with whether Japanese IMs work or not. But for Japanese users in Japan, I believe the situation is quite rare.
 
I understand that if you can't use IM you can't write emails in Japanese, but please don't lump me in with others.
I am writing to say that it is annoying to be thought of in the same way as you.
Please don't generalize with Japanese people.
I haven't said a word about people who don't need to input Japanese.
 
IIRC, Japanese has like 3 different ways of writing: hiragana, katakana, and kanji... and rules for character conversions are quite complex and different from other languages. But Charlie_ , lay off derogatory commentary.

Yeah, the Japanese market for Wayland is different. Yeah, somebody will need to put in programming effort so that Japanese characters render properly on Wayland on FreeBSD. If that happens, FreeBSD would have a much easier time getting accepted in the Japanese market.

Generalization is not easy, but try to reframe it in terms of maybe a 'random sample'. It is an academically valid definition of evidence. If you know anything about statistics, you'd know that much.

Consider this: If a random user says that Wayland-based stuff is nowhere ready for use in their native language because proper character input and rendering sucks, it's time to take that random user seriously. Reacting by saying "You don't represent everyone who speaks your language" is kinda mean in this context.

Oh, and my reaction to this thread's OP?

Unbelievable. GNOME/GTK beating KDE/QT in the race to convert to Wayland? I guess I'll wait for KDE/QT.
 
I'm not a Wayland fan, but I've used RedHat 10 (which is wayland only) on a byve install (running on an X11 system), and it was fine. I've also not had that much problem using Japanese with wayland, using labwc. I put the environment variables that I would put in .xinitrc in ~/.config/labwc/environment. On the other hand, I do use Japanese infrequently, and haven't used it for any long period of time on wayland, and just notice if I can input the characters without paying too much attention to how well or poorly they look.
 
T-Aoki said:
But Japanese people talks, writes Japanese, thus, Japanese IM should work sanely. Do you object this?
Click to expand...

I think it's impractical to expect a software project, conceived from an english-speaking country, to prioritize multi-lingual support. I mean, which is more economically feasible; multilingual support from a projects conception, or simply other foreign users learning the basics of english? I'm not trying to be contrarian, but most of what the world uses (from silicon to software) comes from America.
 
Aside from personal experience users can have and which are expected too and copropartion ( Red Hat blah blah ) vector of critics ( which has the point to a degree of course ) - Wayland protocol is simply better designed and has X.org issues sorted. It is unwise to ignore this part of a story. I use wayland compositors on my thinkpad t480 and window and screen is tear-free, smooth and nice. If i plug my 2nd monitor, all my windows and applications are automatically adjusted with geometry and screen resolution, and fonts are scaled properly and it's again tear-free and very smooth and fast and i did nothing to confiure that. Try doing this with X.org. This X.org/Wayland BSD/Linux, politics, red/blue, left/right are all part of same thing - playing with human nature through "pornography of a doubt".
 
angry_vincent said:
then go and create one that is better.
Click to expand...

Here's the thing. It already exists; i'm using it on macOS. It's called Quartz. :) (which greatly inspired Wayland)

I'm just waiting for that brave soul to write an open source implementation for the BSDs.

To add; Wayland should've been API based, instead of protocol based. Canonical had the right idea with Mir (especially with native EGLStreams support), but they caved to Red Hat, zealots, and Co.

Hail IBM.
 
You must log in or register to reply here.
Back
Top