- cross-posted to:
- linux
- cross-posted to:
- linux
The KDE community has charted its course for the coming years, focusing on three interconnected paths that converge on a single point: community. These paths aim to improve user experience, support developers, and foster community growth.
Very nice.
I’m very excited, because in the past I have bounced off KDE development. Coming from a java and web background, the tooling and dev environment was just mindboggling.
I dunno. Having worked with Java and c#, web dev, c++, I found working with QT in C++ to be so much easier.
Let me be more concrete then. What I am used to is the following:
Every step is a button click or a entry field in a dialog. These steps also work on every major distro. And I wish for a similar experience when developing KDE Plasma.
For completeness, I will try to do the same dev things and list the steps for KDE Plasma development later (in about 8h).
IDEs have come a long way. But I’ve done qt development using Jetbrains Clion IDE and QTCreator. I don’t remember it being that difficult. Then again, I started programming using Turbo Pascal and Turbo C. So …