On Tue, 18 Nov 2025, René J.V. Bertin wrote:
On Sunday November 16 2025 21:25:44 Richard Troy wrote:
asylum" in that younger coders sometimes make silly, occasionally stupid
choices because they just don't know better.
Or, they get involved not because they have a genuine interest in
improving the tools they've already been using but because it can serve
as a useful-for-them project to hone newly acquired skills on,
overhauling things that didn't really need overhauling simply because
there's Something New That's Thus So Much Better.
Great point I neglected!
I was hoping there was some oversight to ensure this wasn't happening, but
apparently I was being an optimist again.
I admit I've contributed nothing to KDE in the way of code (I've spent
most of my open-source attention on Postgres), and I just don't have time
to learn enough about how it works to remove the hugely misguided and
offensive pointer-glue at display boundaries but maybe I can help FIX it:
I offer a bounty of $50 USD, paid via PayPal, for anyone who gets rid of
this ... error .. BUG of an IDEA ... and manages to get it through to
main-stream packaging so I can load it via my standard package
administration. To get paid you've got to show YOU were the one who did
it - or pushed it through somehow without stealing credit from someone
else.
There, is that a good thing? This gawd-awful idea wastes SO MUCH of my
time it's surely worth more than that, especially when considering all the
thousands of others suffering through this truly stupid piece of coding.
If I were more wealthy, I'd offer a lot more.
...OH! And n extra $25 for adding an option to KEEP the god damned
"feature", making sure its selection is NOT the default, as a means of
helping ensure some poor soul doesn't REIMPLEMENT the f-ker when nobody's
looking.
Is that helpful? If this is the wrong venue WHERE do I post my bounty?!
Too bad if it also
requires the latest hardware to run properly ... they have that after
all, no...
ANOTHER great point: Nothing any developer produces should be accepted
until it's been tested on two year old mid-grade hardware as a bare
minimum! This has also been a HUGE source of pain in coding since, oh,
around 1990 or so - the era when the home-schooled became large in
numbers, though most of the atrocious code of that era was well paid for
by the likes of Sun, Oracle, and other big-name outlets as they took on
these ... kids. These businesses were all too happy to push out code that
forced people to upgrade hardware to use because MONEY.
But it's not at all unique to that era; we've been seeing it ever since.
I'm just grateful that since the era of the 3+ gigahertz CPUs, this
problem has been reduced. But then the next stupidity of its type has been
the too-damned-fast replacement cycle making two-year-old code "legacy."
That's SO stupid (but also so prevalent) it's almost beyond words - and
very arrogant, too. What, my TWO YEARS OLD browser is TOO OLD for your
damned web site?! This is YOUR problem! Except when, well, you MUST use
the site.
(Who do I even complain to?!)
Does a 47y pro-programmer have to ask that? Yourself, of course. O:^)
touché
But I addressed the time issue above.
I attribute this to ignorance - not thinking about the multi display
folks
Actually, from what I understand one of the reasons of the move to
Wayland and/or QML/QtQuick is that that solves quite a few issues with
multi-screen set-ups.
-ugh!-
Here's what's wrong with that:
I'm one of the first I ever heard about - probably ever was - to take
three "2 head monitor" cards and have a 6 display system. I first did this
in the mid to late 1990s. Here's that system being upgraded to flat
screens in 2010:
https://sciencetools.com/misc/6_monitor_workspace/
BUT MY POINT IS that I've never had any issues whatsoever with X and many
monitors. Quite the reverse: Wayland failed when X worked flawlessly and
it was a big deal as I started to try KDE.
Your suggestion is exactly backwards.
Wayland was created to help "containerize" our computing, adding needless
overhead (and headaches) for all of us who don't need "containers". The
containerization is needed for virtualization, which divorces user
experiences from the hardware in a way not needed for a genuine live
experience on "raw hardware".
They're trying to compel us to believe x windows is "legacy". I call
bullshit. It's an effort to further push consolidation of computing into
the hands of a few huge enterprises, such as Amazon's massive services,
while hollowing out the rest of the computational world, and at the same
time adding computational cycles - COST - for ALL the rest of us who don't
need it.
DITCH wayland. I've tried. NOW, though, they've introduced a ... I forget
just what they're calling it now ... a translation layer. Even though I've
NOT installed wayland, only x and KDE, it's got this bloatware garbage
between me and the goodness of KDE. -UGH!-
Another reason to have/be circumspect about KDE.
IF ANYONE CAN REFUTE this, by all means, speak up!
R.
Regards, and thanks for pointing out a few important things I missed, and
for giving an opportunity to point out how wayland is an inappropriate
tech for most of us,
Richard
--
Richard Troy, Chief Scientist
Science Tools Corporation
510-717-6942
[email protected], http://ScienceTools.com/
I pledge allegiance to We, The People, to mutual peace and harmony, and
to the natural Earth and biosphere upon which We, The People, depend.
