Not everything made by KDE uses C++. This is probably obvious to some people, but it’s worth mentioning nevertheless.
And I don’t mean this as just “well duh, KDE uses QtQuick which is written with C++ and QML”. I also don’t mean this as “well duh, Qt has a lot of bindings to other languages”. I mean explicitly “KDE has tools written primarily in certain languages and specialized formats”.
Note that I said “specialized formats”. I don’t want to restrict this blog post to only programming languages.
I’ll be straight to the point. You can contribute to KDE with:
- Python
- Ruby
- Perl
- Containerfile / Docker / Podman
- HTML / SCSS / JavaScript
- Web Assembly
- Flatpak / Snap
- CMake
- Java
- Rust
Here’s how.
Of course, Python will always be slower than C/C++. But you’ll only notice it’s made with python if it is slow, otherwise you won’t even think about it. Many system utils use it, for the convenience of ArgumentParser etc., but as they follow the principle of doing one thing only, but very quickly and well, you’ll not even notice the difference between it being written in python, running for 0.1s, and C, running for 0.01s.
Is this an empty excuse lol?
Now add 10 or 50 things like that together and see the difference. One thing never makes a difference but it’s a combination of all of them that does. Ask ecologist for example.
Chaining that together would make a difference if the whole DE would be written in Python, and only on startup. Almost everything you do is broken down into very simple instructions anyway. Instructions that run in milliseconds in every language.
Sorry but your excuses only defend Python and induce bloat and planned obsolescence.