Not really visudo is only to edit the sudoers file. sudoedit is a better way to edit system files.

1. Temporary copies are made of the files to be edited with the owner. set to the invoking user.

2. The editor specified by the policy is run to edit the temporary files. The sudoers policy uses the SUDO_EDITOR, VISUAL and EDITOR environment variables (in that order). If none of SUDO_EDITOR, VISUAL or EDITOR are set, the first program listed in the editor sudoers(5) option is used.

3. If they have been modified, the temporary files are copied back to their original location and the temporary versions are removed.

That already exists. systemd-run is already available today. So the attack surface would be smaller

I think the article (or more Lennart Poertting post) explains it quite nicely. The problem with sudo is that the sudo binary itself has the ability to gane elevated privileges which is a potential attack surface

The only problem I found was, that it has no real alternative to sudoedit

You can edit the accepted sizes under Settings > Quality

You can collapse the subwindows and configure the graphs

There is a good quote from Bjarne Stroustrup for that “There are only two kinds of languages: the ones people complain about and the ones nobody uses”. I think for hobby projects it’s the best to use languages that interest you

Flatpak is a linux package format. Bottles is a gui software that makes it easy to run windows software (especially games) on linux (it is a very good gui/management tool for wine)

If you use meson or cmake, you can generate a compile_commands.json which you can link from the build dir into your source dir. If not you cam create a local config file for clangd https://stackoverflow.com/questions/73758291/is-there-a-way-to-specify-the-c-standard-of-clangd-without-recompiling-it

I mean if oyu don’t like it, then don’t use it or install an extension. I never missed a bar at the bottom and can find all open windows in the overview very quickly