4 ms·
Thanks! I come from the embedded world and my preferred language is C - hence the need for a calculator that can wield bits like this. I wrote this tool around
by fellerts 4y ago
Thanks! I come from the embedded world and my preferred language is C - hence the need for a calculator that can wield bits like this. I wrote this tool around 4 years ago and it was my first attempt at creating anything that wasn't a CLI tool or bare-metal firmware. In other words, I can't really compare this experience to anything!
I guess the reason I chose Qt over any web-based frameworks is I wanted a standalone app that would launch in a fraction of a second and just do its job. I don't think a webapp (if that's what they're called) would give me that. At the time, it seemed that Qt would work well and, as a bonus, be cross-platform. I had some Python experience to boot which helped.
Edit: I do have a personal site at https://www.fellerts.no/ https://www.fellerts.no/ but it's entirely static, no real js to speak of.
- billfruit 4y agoBut Qt is a quite huge dependency, and has sort of turned into a commercial product. If you were starting to develop something similar today would you still choose Qt for it..
- fellerts 4y agoGood 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
- ognarb 4y agoQt is not turning into a commercial project. It has always been a project which is dual licensed under GPL (and later some of the modules were also licensed under LGPL) and a commercial license. It's just that the Qt company always tries to make it non-clear that Qt is not open source to drive their sales. Regarding bloat, Qt is quite modular and if you want just the widgets you only need QtBase and none of the additional modules.
- ranger_danger 4y agomost components are LGPL not GPL. also after I think it was Qt 5.6, they switched to LGPLv3 instead of v2, so the anti-tivoization clause applies.