3 ms·
Yes, closed source libraries are a pain to work with. This is why I like the GPL/Commercial dual licensing model. You can try it out for as long as you like, ha
by Lariscus 2y ago
Yes, closed source libraries are a pain to work with. This is why I like the GPL/Commercial dual licensing model. You can try it out for as long as you like, have full access to the source code and can even create commercial software for free. You are only required to pay for a license if you want to create closed source software. I consider this an absolutely fair deal, yet the blog author seems to take issue with that which is what I am criticizing.
- zer0zzz 2y agoThat’s fair in theory, but it really feels that they’ve made it more difficult to find the open source version of Qt last I checked. I haven’t tried to use it in a while, but I recall last time I tried I just gave up.
- Lariscus 2y agoUnfortunately they do and they really try to scare you away with the GPL boogeyman. It is a fair criticism. I would recommend to ignore the installer entirely and rely on a package manger like vcpkg, conan, apt, or brew instead. You can find the manual installer here: https://www.qt.io/download-qt-installer-oss https://www.qt.io/download-qt-installer-oss
- zer0zzz 2y agoYeah I should have just used brew. I was trying to find the package for Mac a while ago to see if I could write some swift bindings. I moved on to messing around with some other library for my experimentation.