> With Qt you also have to use its own classes for non-UI stuff, like strings and lists. At least for the parts interacting with Qt components and yes, that ca

> With Qt you also have to use its own classes for non-UI stuff, like strings and lists. At least for the parts interacting with Qt components and yes, that can be an annoyance. Tricky tradeoff with compatibility and performance optimizations. On the other hand, it also gives you a bunch non-GUI things that otherwise would need extra libraries. > It’s also pricey for closed source. Given the author is clearly talking about Windows (=desktop) applications, I don't see why they think using Qt under LGPL is not an option for them.