Qt 5.5 Released
New submitter mx+b writes: The latest version of Qt, the cross platform GUI toolkit and development platform, is out for all major platforms. Highlights include better 3D, multimedia, and web support, as well as better support for the latest OS X and Windows releases (including Windows 10) and more Linux distributions.
until its functionality gets folded into systemd.
Thankfully OSX, Windows, Android, iOS and Windows Phone aren't burdened with systemd like the Linux desktop is.
When I've read "web support" I though "Cool! I will finally get good support to run QT apps on a standard browser". But alas, it just means running a Chromium engine embedded in a QT app. Who wants to run web sites in an app nowadays instead of opening them directly in a browser?
Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
QT is modular. This allows them to add features (you call it bloat, but I don't think it means what you think it means), and then it is up to application developers to pick and choose the modules that they want or need.
The demand for more features is omnipresent, and software developers can either choose to fulfil them one way or another, or lose their market share to someone else who does.
QT is a huge stinking pile of bloatware. I eschew it.
You are right, QuickTime is bloatware. However, Qt is well written and you are given the option to build only what you need and which libraries it should use. The render engine is exceptionally flexible too, allowing it to leverage many different methods of rendering. Don't have X? no problem, add a runtime argument (-platform linuxfb) and your qt program will display using the linux framebuffer. Qt also builds for desktops (e.g. Linux, Windows) and embedded systems (e.g. Android, iOS) and is easy to cross-compile for your device of choice.
if you think GTK+ is slimmer, guess again and check your binaries.
Anons need not reply. Questions end with a question mark.
One of these days I'll have to get "into" QT. It looks like a great successor to some of the concepts originating with Neuron Data's tools, which I spent a lot of years learning and working with. For now I've been focused on Java server code, but I've never really been a fan of Java for writing client applications, and I've no interest in buying an Android device just so I can stick with Java while working on front-end code.
No, to me, client side means an actual computer, not a mobile device. And QT hits almost as many platforms as Java does, so it would seem to be an excellent fit for my goals. :)
I do not fail; I succeed at finding out what does not work.
yawn... that is getting very old now, can't you think of anything original?
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
they all have their own versions..
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
" bloatware" is always used by people who don't know what they are talking about.
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
"bloatware" is always said by people who don't know what they are talking about.
pff! that's a bunch of bloatware!
Anons need not reply. Questions end with a question mark.
Qt is not just a GUI toolkit. Doxygen has been using it for years. I do high performance computing and copy-on-write data structures (as Scott Myer suggest a decade ago in "More Effective C++") means I don't have to worry about functions returning references to a std::vector because QVector's copy constructor is O(1) as Scott Myers recommended a decade ago. I have a sane cross-platform cross-DB SQL interface. My strings are Unicode (and copy-on-write).
Qt allows you to write high performance code but in a style closer to Perl (especially with 11. "Auto" is "my") while enabling a coder to use high performance C code without needing to write fancy interfaces and compile schemes Everything from threading (QtConcurrent is great!) to file access to JSON to regex to is well-documented and the compile errors are sane (see: boost) and the code is terse (also: boost).
If you're doing serious C++ development with a small team, Qt is the best way to get things done in my experience...and it's also trivial to make a GUI to represent a SQL query.
-- Political fascism requires a Fuhrer.
QT is a huge stinking pile of bloatware. I eschew it.
You are right, QuickTime is bloatware. However, Qt is well written and you are given the option to build only what you need and which libraries it should use. The render engine is exceptionally flexible too, allowing it to leverage many different methods of rendering. Don't have X? no problem, add a runtime argument (-platform linuxfb) and your qt program will display using the linux framebuffer. Qt also builds for desktops (e.g. Linux, Windows) and embedded systems (e.g. Android, iOS) and is easy to cross-compile for your device of choice.
if you think GTK+ is slimmer, guess again and check your binaries.
I was bored at work and checked libqt5core and libqt5gui vs gdk/gtk. Those two qt5 components amount to ~10 MB vs ~5MB for gdk/gtk. QtQuick probably gets that well over 20MB.
But you're not going to use either on some Cortex-M MCU anyway, so who cares.
$4200 per year per developer! My interest in Qt just fell off a cliff
sure, but I thought gtk had a dependency on systemd nowadays so you have to count it's, and all its dependants' binary sizes too :-)
Agreed. It there a worse C++ library? Perhaps Boost. Qt should be rejected for its slots and signals alone.
and is easy to cross-compile for your device [doc.qt.io] of choice.
For some value of "easy"... Ever seen Go? Or Oberon?
Thankfully OSX, Windows, Android, iOS and Windows Phone aren't burdened with systemd like the Linux desktop is.
All those operating systems run a service daemon similar to SystemD.
Hey, if you really want it, some BSDs and Linux distros still allow you to run an init based on crusty text scripts and text configuration files, just like AUTOEXEC.BAT and CONFIG.SYS in the DOS days.
> and embedded systems (e.g. Android, iOS)
Qt for embedded is not open source.
How well does using Qt for iOS and Android development work? Last I checked, the documentation on how to effectively utilize Qt for this purpose wasn't nearly as informative as using it for it's more traditional use case. I would love to be able to do cross platform mobile development using C++.
QT Mobile was a total farce and joke.
We dumped it after attempting to do a project on it. TOTAL FAILURE.
NEVER AGAIN will we believe cross platform claims. Total hype, lack of features, total fail.
QT is a huge stinking pile of bloatware. I eschew it.
You are right, QuickTime is bloatware. However, Qt is well written and you are given the option to build only what you need and which libraries it should use. The render engine is exceptionally flexible too, allowing it to leverage many different methods of rendering. Don't have X? no problem, add a runtime argument (-platform linuxfb) and your qt program will display using the linux framebuffer. Qt also builds for desktops (e.g. Linux, Windows) and embedded systems (e.g. Android, iOS) and is easy to cross-compile for your device of choice.
if you think GTK+ is slimmer, guess again and check your binaries.
I live in Montreal -- two official languages French/English. I also do development for Latin America. QT bloatware is great. User selects his language and there we are, one software for E/F/S.