What can be done to make the Qt toolkit and KDE technologies more attractive?

• Killed by Google

  2,301 2,345 6.9 TypeScript

  Part guillotine, part graveyard for Google's doomed apps, services, and hardware.

I'll add this in case anybody thinks you are being serious. https://killedbygoogle.com

• themix-gui

  19 2,018 7.8 Python

  Graphical application for generating different color variations of Oomox (Numix-based) and Materia (ex-Flat-Plat) themes (GTK2, GTK3, Cinnamon, GNOME, Openbox, Xfwm), Archdroid, Gnome-Color, Numix, Papirus and Suru++ icon themes. Have a hack for HiDPI in gtk2. Its Base16 plugin also allowing a lot of app themes support like Alacritty, Emacs, GTK4, KDE, VIM and many more.

  

There's also an open ticket for oomox to be able to export a Kvantum theme.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• dmd

  146 2,888 9.9 D

  dmd D Programming Language compiler

  

The D language, which is aimed at being a better C++ alternative, describes the issue as well as how they deal with it. The solutions it lists as the usual choices are "use COM for Windows", "write a C wrapper", "write a tool that writes the C wrapper for you", "rewrite it in something that isn't C++", and "give up".

• QMetaObject crate for Rust

  20 600 6.5 Rust

  Integrate Qml and Rust by building the QMetaObject at compile time.

  

On the other hand, there isn't a need to have bindings for all of Qt, only enough of Qt to build a GUI. Qt provides lots and lots of libraries, many of which are no needed for building GUIs and could be provided by libraries in other languages. This is the approach the qmetaobject Rust library takes.

Suggest a related project