3 ms·
Good question. If I want fast and cross-platform, GTK might be a more viable option today. What would you choose for a project like this in 2023?
by fellerts 4y ago
Good question. If I want fast and cross-platform, GTK might be a more viable option today. What would you choose for a project like this in 2023?
- billfruit 4y agoSome years ago JavaFx would have been a reasonable choice.
- ranger_danger 4y agoQt hands down. I don't consider GTK particularly usable or friendly, especially outside of Linux.
- oynqr 4y agoThis is so bad, even on Linux, that the experience of trying to package a GTK4 libhandy application to the distro I use made me permanently switch from Gnome to KDE.
- criddell 4y agoI'd pick the native toolkit for wherever I want to use it. If I want it on Windows, I'd use C++ & Win32 / WinRT. On mac, Swift + AppKit. For iOS, Swift + UIKit. For Linux, probably C and GTK (I mostly use Gnome-based distros). I'd go 100% native because that's how you make the best app for that platform. I also enjoy working with different toolkits and if I wanted this on more than one platform, I think I would enjoy designing and building it for different environments. For example the version I'd make for my small screen touch-based phone would probably be significantly different than what I'd want on my keyboard and mouse equipped big screen desktop. A multi-platform or web-based solution would have too many compromises.
- jenadine 4y agoSlint? https://slint-ui.com https://slint-ui.com