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.

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.

  • deejay4am@lemmy.worldEnglish
    0·
    2 months ago

    I always kind of thought of KDE as “okayish” but ever since plasma 6 I’m a convert! Hope to see some excitement for these projects in the coming years - it feels to me that KDE is reaching a maturity that could attract a critical mass.

  • penquin@lemm.ee
    0·
    2 months ago

    Python to me is much easier to write than C++, so I very much welcome this goal. Thank you

    • m4m4m4m4@lemmy.worldOP
      0·
      2 months ago

      Not an expert programmer whatsoever, and it’s been more than 15 years I’ve used Python for doing something GUI related (it was Python 2 and GTK+2…), but I do know you can do KDE stuff with Python right now. For example, there are Kirigami bindings for Python you can use to do a desktop/mobile app.

      Still though I absolutely agree getting into C++ is a nightmare, to me is just a level behind Assembly and Brainfuck. I’d like to learn Rust and it’d be great to be able to contribute to KDE with it.

      • Herzenschein@pawb.socialM
        0·
        2 months ago

        A small correction:

        For example, there are Kirigami bindings for Python you can use to do a desktop/mobile app.

        Kirigami is QML all the way, it doesn’t need bindings since you’d be writing in QML either way. The Python part is about the actual business logic. :)