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.
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.
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?
Oh? Would you mind sharing them? It would be absolutely fantastic if such a thing existed and is mature enough to be practically used.
FFI, bindgen/cbindgen, cxx/autocxx, zngr, cpp crate, diplomat, crubit
Dang, that’s pretty neat! Man, there’s probably going to be some funky bugs with legacy code getting included into Rust.