Am bored so going to ramble some more on this.
End of the day believe personal users aren't the focus when it comes to the future of gnu/Linux and much other FOSS. Huge chunks of the upstream and major components are paid for by commercial interests. From the kernel to so much else, Wayland, audio etc etc etc. So since they have the skillset, the standing and the check book, needless to say they're going to push their agenda, with I'm guessing an emphasis on commercial, industrial, business applications rather than joe-smoe end user who gets to use all this kickbutt software for free. So whether that be as in this case trying to make the platform more secure, or the focus is stability or whatever else, think the relevant parties will continue to focus on commercial implications. Stuff like this is a walk in the park for any seasoned sys-admin. For that matter any desktop nixer willing to invest some effort. They'll either embrace it or employ whichever work-around suits their needs. Not that there aren't still plenty of volunteer contributors, nor that Debian doesn't care about the personal computing users anymore either. Am sure they do, as well as who knows how many open source projects dev'ed by kickbutt people too. Though still are going to be subject to major decisions made upstream. Just that it is, what it is and overall what we have to work with or around.
Mentioned (and it was confirmed by Wizard10000) no reason gksu won't continue working fine in Buster, not sure what issue you're having with lxqt-sudo either. Can't fathom why there'd be any problem, in particular if someone opts to continue using Xorg vs Wayland. Should be business as usual in such a case. Could be desktop dependent I guess, don't know, have always prefered windows managers anyway so haven't invested much effort in keeping up with Kde/Gnome developments. To me it's totally reasonable that end-users (particulary those which contribute nothing meaningful, other than their free use and enjoyment of the available software)be expected to learn and do something for ourselves. Rather than "I don't like this, change it, do it automagically for me." Yep, only 24hrs in a day and Google is open 24/7/365. Solutions are never far away in my experience.
I don't quite get it either, if someone with the creds wants to launch processes as root, with no "finer grained control", they can do it. If someone with the system credentials wants to nuke a node or an entire network, they can do it, shrugs. Somehow polkit with policy files is better. It's above my pay grade, I don't have a fraction of the skills or understanding of the FOSS big picture that the people behind such decisions do. So just have to find a setup that fits my preferences and get on with life. Which in my particular case will likely be lxqt-sudo (with a bash alias.) or some similar work around. This has been a pointless brainfart babbling moment about some of my views on FOSS.
.
