Qt long steep learning curve & expensive price!

? Offline · 6 Apr 2019, 17:15

@raven-worx said in Qt long steep learning curve & expensive price!:

note, that QtWebAssembly uses static linking (means no LGPL here), so you will have to ship the source code if you want to use it commercially anyways.
For mobile platforms only LGLv3 is available (with newer Qt versions) so still no commercial apps without publishing the source. if you have no license.

This brings me once again to the first post, Qt is very expensive for freelancers and small companies :(

raven-worx · 4 Jun 2019, 18:49

@Mehmet-Yilmaz
yes unfortunately. There was once a start-up license available which was definitely effortable even for one-man companies, but they ditched it

SGaist · 6 Apr 2019, 21:37

@raven-worx said in Qt long steep learning curve & expensive price!:

QtWebAssembly uses static linking (means no LGPL here

One note about this statement: this is wrong.

Static and LGPL is possible however, the constraints makes it usually complicated enough that people rather go with dynamic linking.

See the links provided in this stack overflow answer.

raven-worx · S SGaist 6 Apr 2019, 20:44

@SGaist said in Qt long steep learning curve & expensive price!:

One note about this statement: this is wrong.

ok you are right. my answer wasnt complete.
But i am not sure if this is still the case also for LGPLv3?

Anyway it seems the open source license for QtWebAssembly platform plugin is GPL.

? Offline · wrote on 6 Apr 2019, 22:33

Thanks a lots guys for the nice replies.
Unfortunately, It seems I'll go with Xamarin because it's much cheaper.

shaan7 · wrote on 7 Apr 2019, 07:09

@Guest said in Qt long steep learning curve & expensive price!:

I forgot to mention that I failed to create Qt app supports RESTful so I used Felgo instead! But in Xamarin I did with first Google result I got!!!

Just asking out of curiosity. What do you mean by "supports RESTful"? REST is just a guideline on how to design server-side HTTP API. You can consume any HTTP API from Qt C++ (via QNetworkManager) or even from QML by using standard JavaScript XMLHTTPRequest without using Felgo. I do it all the time for our app which talks to our RESTful API server.

ABponant · wrote on 9 Apr 2019, 06:45

Sure $5000 a year per developper is a very excessive price.
It may be smiling for companies like Audi but disqualify Qt on small markets at a time where most of the Developement Environments are free.

Sure one could argue that a LGPL solution is available for free, but commercial projects cannot choose such solutions.

I today have no idea about runtime fees but I guess it would be maybe better to increase a little bit runtime fees (variable costs) and drastically decrease developper licence cost (fix costs).

Alain

fcarney · 26 Apr 2019, 19:16

For what Qt brings to the table even if licensing it at $5000 a year, it can shave off man years in development. It is a very useful environment to learn and use. Definitely would have been easier to learn than Turbo C++ was to learn 25 years ago. It provides complete development tools that don't time out or require logging into the vendor so they can spy on you. LGPL licensing is more than flexible enough for commercial development. The LGPL licensing require zero dollars in royalties. It can easily help a starting developer bootstrap their company/projects for zero cost paid to the Qt company. They have people (not sure of affiliation) readily willing to help you in the forums to solve just about anything you run into. People ask basic questions from "How to make a string in Qt?" to "How do you parallelize an app?" You cannot put a price on that alone. Qt is a swiss army knife that keeps adding blades (and their sharp). Every release has some new feature that many of which I didn't know I needed until I saw it in Qt. It is an amazing set of tools, libraries, and development ecosystem. I have used other GUI systems and many times finding solutions take days if you ever find a solution. Qt is the inverse of that. Google any CS topic and the word Qt and you will either find a discussion about it, working code, or a Qt reference in the Qt documentation explaining how to use the topic.

My biggest complaint with Qt: Where have you been all my life?

aha_1980 · wrote on 26 Apr 2019, 19:16

@fcarney

They have people (not sure of affiliation) readily willing to help you in the forums to solve just about anything you run into.

Indeed, most of us are not affiliated with The Qt Company and help in our free time in the forum, the mailing lists, at the code and bug report front.

And we do that, because the Qt community is such a great place, and anyone is welcome.

Thanks for your nice post, I fully second it.

Pablo J. Rogina · wrote on 26 Apr 2019, 19:25

@Guest said in Qt long steep learning curve & expensive price!:

why I need to pay money for Qt guys and Felgo?! This is absolute madness!

this part caught my attention deeply. Those are companies providing a service that you may find interesting, and that may help you solve your problem(s) so why not?

I'm planning to start my own -one man- company

In that case, aren't you planning to be paid money? It looks like you'll be at the same level of Qt or Felgo right?

johnnydel · wrote on 23 May 2019, 20:20

This post is deleted!