Re: Both KDE and GNOME to offer official distros

rbowman wrote this post while blinking in Morse code:

https://www.theregister.com/2024/11/29/kde_and_gnome_distros/
>
I've got to admit I wonder why. I never thought of KDE as European and
GNOME as American even though I started using KDE with SuSE, Qt always had
licensing problems but I never could warm to functions like
gtk_native_get_surface_transform().  Damn API could wear out a keyboard.

Those motherforkers!!!

I forked a project that used Gtkmm (a wrapper around Gtk) and I liked many
aspects of it better than Qt. But when I forked my fork, I decided to go with
Qt for a couple of reasons. (1) I started with the code of another fork of the
project, which used Qt, and it made it easier for me to gain traction; and
(2) Looking around, it seemed (and still seems) that Qt's cross-platform
support is a bit more reliable (for various meanings of reliable).

Of course, I reworked the fork heavily to my exacting standards, used code in
the std namespace (e.g. std::string rather than QString) for the internal
project API, and wrote some Qt "helper" functions to centralize things like
adding icons to buttons.

As for using a lot of keystrokes...

    https://www.lysator.liu.se/c/ten-commandments.html

    6  If a function be advertised to return an error code in the event of
    difficulties, thou shalt check for that code, yea, even though the checks
    triple the size of thy code and produce aches in thy typing fingers, for if
    thou thinkest ``it cannot happen to me'', the gods shall surely punish thee
    for thy arrogance.

I don't follow C commandments 8 and 9, though.

--
You know you have a small apartment when Rice Krispies echo.
-- S. Rickly Christian