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.
I need proper and maintained bindings for languages that can and know how to talk to the only portable interface, which unfortunately is C ABI.
With proper docs not referencing and jumping around to unreadable Cpp docs or sources on other places or not giving enough info inline and defering to the weird Qt docs and their custom compiler plugins.
Give me proper ways to build apps integrated without having to jump around and learn 3 technologies I absolutely despise and have no interest on interacting with.
This is my want to be able to create apps on kde.
Although the blog is about all the ways one can contribute with their experiences to the project, I still feel this would bring a lot more eyes and apps to the platform.