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.

    • Kalcifer@sh.itjust.works
      102·
      2 months ago

      Personally, I have little interest in learning or dealing with C++ solely for the sake of developing KDE applications. I would much rather use Rust.

      Imo, restricting the languages that can be used for app development cuts out large swaths of developers who would otherwise be eager to develop software for the project. I’m sure there are some who wouldn’t mind picking up C++ for this cause, but I’d wager that they are a minority. Gnome beats out KDE in that regard, imo, as GTK has bindings and documentation for many languages.

      • refalo@programming.dev
        41·
        2 months ago

        I thought Rust already had several different methods for interacting with C++? I’m not sure what actual roadblocks there are to developing KDE apps with it?

        • Kalcifer@sh.itjust.worksEnglish
          3·
          2 months ago

          I thought Rust already had several different methods for interacting with C++?

          Oh? Would you mind sharing them? It would be absolutely fantastic if such a thing existed and is mature enough to be practically used.

    • carzian@lemmy.ml
      4·
      2 months ago

      The success of KDE depends on maintaining and attracting new developers. C++ is decreasing in popularity, with less people becoming willimg to learn it overtime. Adding more modern languages to the mix that are more pleasant to write with will help keep KDE popular with devs.

      • refalo@programming.dev
        9·
        2 months ago

        So blown out of proportion. Nobody is saying to stop using them. The report is more of a state of the union on software in secure systems and the talking points hinge on the most common type of vulnerability seen in large scale attacks: memory safety.

        The report (which apparently barely anyone is reading) mentions C/C++ aren’t memory safe (truth) and with specific respect to space flight, alternatives such as Rust haven’t been proven yet. Both languages meet other important criteria (again specific to space flight) but it then immediately states afterwards that until other languages can be qualified, other means of ensuring memory safety are recommended such as hardware. The report makes other mentions. It’s a good read but is not a directive like media is making it.