Bounty on Pointer BUG - was Re: Konqueror bugs

[René J.V. Bertin]

On Tuesday November 18 2025 22:53:59 Richard Troy wrote:

>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.

It might be the opposite; I think there are a few key persons in ditto places (on ditto projects) who are very, erm, progressive. There's quite a bit of code that's probably "easy" to maintain, but really not accessible to anyone not familiar with very recent C++ standards.
(That said, anything that really exploits virtual methods etc. can be a real pain to triage if you want to figure out where something goes wrong, but I digress).


>Is that helpful? If this is the wrong venue WHERE do I post my bounty?!

$75 might not impress a lot of script kiddies nowadays ;)
This is the generic list which seems to attract mostly users. Assuming things haven't changed you should probably consider posting about it on the plasma-devel ML, or check if there's a KDE Plasma related IRC channel. And file a ticket on bugs.kde.org (BKO). 


>> 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 


I'm a (former scientific) user turned developer because I had to create my own tools (or was moved to bc the available ones were clearly never used by the peope who developed them ... another golden rule IMHO), and given that background I was already used to not being able to upgrade computing hardware on a regular (pardon, frequent) basis. 

>these ... kids. These businesses were all too happy to push out code that 
>forced people to upgrade hardware to use because MONEY.

That's still going on. Try to run a recent MS or Apple OS on older hardware. The latter, also a seller of hardware, won't let you (and IMHO since they also sell disk space they also don't incentivise developers to keep the size of software down.)
 
>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.

Sadly, not just their problem. With browsers having become a kind of virtual machine running some kind of OS (complete with direct USB access and what not) and used for sensitive operations you as a user run risks when using an outdated browser, and the site operator too in a way.

>BUT MY POINT IS that I've never had any issues whatsoever with X and many 
>monitors.

X11 itself doesn't have issues, no. Not as long as you don't expect a lot of DE fancyness.

>Your suggestion is exactly backwards.

I'm just repeating what I remember of what I understood of what someone tried to explain to me when I complained about the use of QML. X vs. Wayland is mostly moot for me, for now.

>They're trying to compel us to believe x windows is "legacy". I call 
>bullshit.

It *is* old, and it also comes with its own overhead. Things like "quality" video playback are a bit "grafted" on. (I can get perfect-for-me, tearless video playback in a few dedicated applications on my Linux machine, but not in my browser even though I can see it uses the propre VAAPI stuff).
Integrating the window manager and the renderer (as in KWin) does make sense.

> for giving an opportunity to point out how wayland is an inappropriate 
>tech for most of us,
>

>From a scientist's point of view that may be true, IIUC basically because "X11 terminals" are still very much a thing in a number of disciplines. I was in a different discpline where X11 was a less obvious choice unless you had money to spend on high-end graphics workstations from the likes of SGI.
Most "joe users" will probably only notice that things run a bit smoother under Wayland. That at least was my impression when I tried a more modern distribution on familiar hardware, without being aware they it used Wayland.

R.