Hi everyone, there's something that has been baffling me and probably many other non-English users: Why don't Linux distributions pre-install and integrate the "trio" of input frameworks—XKB, IBus, and Fcitx - directly into the system, and simply let the user choose their preferred option during or after installation? Why do they still only default to XKB?

Currently, I see a lot of people giving up on Linux simply because of this input method barrier.

For context

I am a Vietnamese user who transitioned from Windows. On Windows, we just need to download a lightweight tool like UniKey (or in the past, VietKey, WinVNKey, or ABC). Once downloaded, we just run it and basically forget about it. It requires minimal to no configuration, and it just works across the entire OS because it acts as a proper hook/IME layer.

The inherent flaw of XKB for complex scripts

Let's be honest, XKB's design is fundamentally flawed and outdated when it comes to input methods like Vietnamese Telex. XKB treats Telex as if it were just another static keyboard layout using dead keys. It lacks any concept of an active text buffer or smart processing.

For example, tools like UniKey on Windows handle Telex dynamically (allowing users to type the tone mark at the end of the word, e.g., c-h-u-o-n-g + w = chương, t-r-i-n-h + f = trình). XKB completely fails at this because it can't look back at the characters you just typed. Trying to force Telex into XKB's 1:1 or simple dead-key mapping matrix is just painful and unusable for daily communication.

The current state of Linux (and why average users hate it)

To get basic Vietnamese typing working on a fresh install, a casual user is forced to follow a manual "tutorial" that looks like this:

1. Install the engine via Terminal: Since these IMEs are rarely in the default Software Center GUI, they must copy-paste commands to add external repositories and install packages: sudo apt update && sudo apt install ibus-bamboo (Or deal with the AUR/Pacman if they are on Arch-based distros: sudo add-apt-repository ppa:bamboo-im/ibus-bamboo).
2. Manually configure System Environment Variables: They must open a text editor (often as root) and append these lines to /etc/environment, ~/.xprofile, or ~/.pam_environment: GTK_IM_MODULE=ibus; QT_IM_MODULE=ibus; XMODIFIERS=@im=ibus
3. Register the Input Source: Log out, log back in, open GNOME/KDE Keyboard Settings, search for "Vietnamese", and manually add the newly installed engine to the list.
4. Fix Flatpak / Snap Sandbox Issues: Realize that modern apps like Discord, Steam, or Spotify (installed via Flatpak/Snap) cannot type Vietnamese out of the box. They now have to install another app like Flatseal or run complex terminal overrides just to let the IME pass through. (This is especially a nightmare for IBus users and Electron-based apps on Wayland).

It is already 2026. Why can't we simplify this process out of the box the way Microsoft does with its built-in IMEs? I understand that forcing a single monolithic solution might go against modern Linux design philosophies.

But why can't we design a unified system settings GUI that pre-configures and integrates all three frameworks behind the scenes? The setup process for a user should be as simple as choosing:

1. Language (e.g., Vietnamese)
2. Framework/Engine (e.g., XKB vs. iBus vs. Fcitx - where the OS automatically handles the environment variables and sandbox permissions in the background)
3. Layout/Input Method (e.g., Telex, VNI, or US Layout)

What are the architectural, historical, or philosophical reasons keeping distros from making IME a first-class, pre-configured citizen alongside XKB, instead of forcing us to deal with an outdated framework that doesn't understand modern input methods?