LWN: Comments on "Qt 5.5 Alpha Available" https://lwn.net/Articles/637033/ This is a special feed containing comments posted to the individual LWN article titled "Qt 5.5 Alpha Available". en-us Wed, 15 Oct 2025 08:41:33 +0000 Wed, 15 Oct 2025 08:41:33 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Qt 5.5 Alpha Available https://lwn.net/Articles/637259/ https://lwn.net/Articles/637259/ Sho <div class="FormattedComment"> Unfortunately back then, Qt was under an open license (GPL) but didn't have open governance yet. It was very difficult to get code into Qt without being a Trolltech employee. So this wouldn't really have worked for either side. The situation has changed only fairly recently, but dramatically for the better - KDE has directly contributed a lot of code to all Qt 5.x releases, hosted the Qt Contributor Summit at Akademy and KDE people act as maintainers for a bunch of areas of the codebase.<br> </div> Thu, 19 Mar 2015 12:50:22 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637236/ https://lwn.net/Articles/637236/ niner <div class="FormattedComment"> Using KHTML as new rendering engine was a very good idea. After seeing both Gecko's and KHTML's source, I'd have clearly made the same choice.<br> <p> What they did _not_ have to do was forking KHTML and developing it behind closed doors for years before being pressured into opening up.<br> </div> Thu, 19 Mar 2015 07:58:38 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637230/ https://lwn.net/Articles/637230/ pabs <div class="FormattedComment"> They should have talked KDE folks into moving KHTML to QtHTML instead of forking off into WebKit.<br> </div> Thu, 19 Mar 2015 05:49:12 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637213/ https://lwn.net/Articles/637213/ Sho <div class="FormattedComment"> Ironically, Mozilla's Servo team is currently implementing the Chromium Embedded Framework (CEF) API to allow embedding the new engine into applications for real tests.<br> </div> Thu, 19 Mar 2015 00:41:59 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637206/ https://lwn.net/Articles/637206/ nix <div class="FormattedComment"> Actually you have a bunch of Mozilla developers who'd been through the fire and decided, when the time came to build a new rendering engine for their then employer (Apple) to use KHTML instead.<br> <p> This wasn't a corporate-insanity thing. It was a "we've been there, Gecko is not usable for this" thing.<br> </div> Wed, 18 Mar 2015 23:26:06 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637162/ https://lwn.net/Articles/637162/ jreznik <div class="FormattedComment"> QtLocation is not new thing, it dates to Qt 4 and Nokia. And it's pretty useful to have mapping widget and location module for mobile apps (almost every single mobile application shows some kind of map). It even isn't that new in Qt 5 but now it's (almost) officially back. I use it in one of mine mobile apps as of Qt 5.3. Yes, you can write your own component but why if you want to show a few pins on map with your current location? Same applies for QtMultimedia. <br> </div> Wed, 18 Mar 2015 17:41:57 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637100/ https://lwn.net/Articles/637100/ niner <div class="FormattedComment"> And we have Apple to "thank" for it.<br> </div> Wed, 18 Mar 2015 10:14:08 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637084/ https://lwn.net/Articles/637084/ pabs <div class="FormattedComment"> I swear KHTML is the most forked software in existence apart from the Linux kernel.<br> </div> Wed, 18 Mar 2015 03:06:50 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637077/ https://lwn.net/Articles/637077/ Sho <div class="FormattedComment"> Qt's included a copy of WebKit (the browser engine originally forked from KDE's KHTML) for many years now, and there are many desktop browsers playing frontend to that library, among them KDE's Rekonq, QupZilla and Arora.<br> <p> What's new here is that Qt 5.5 has formally deprecated the Qt WebKit module, in favor of the new Qt WebEngine module instead based on Google's Chromium/Blink fork of WebKit. Qt WebEngine was originally added in Qt 5.4. WebEngine means newer code and better integration into Qt's modern rendering pipeline, enabling some newer web technologies, vs. the older (but until recently still lightly improving, e.g. 5.4 made Canvas2D GL-accelerated) WebKit module.<br> </div> Wed, 18 Mar 2015 00:00:56 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637064/ https://lwn.net/Articles/637064/ sjj <div class="FormattedComment"> I don't know how much you're exaggerating, but that's kind of [awesome|disturbing]. I hope somebody runs with a thin frontend idea...<br> </div> Tue, 17 Mar 2015 22:36:09 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637060/ https://lwn.net/Articles/637060/ flussence <div class="FormattedComment"> Qt5 is almost a feature-complete replacement for Firefox at this point. All it's missing is a decent frontend... sadly Konqueror died years ago.<br> <p> Let's hope it doesn't become antifeature-complete also.<br> </div> Tue, 17 Mar 2015 22:13:25 +0000 Qt 5.5 Alpha Available https://lwn.net/Articles/637045/ https://lwn.net/Articles/637045/ proski Remember Zawinski's law? <blockquote type="cite">Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.</blockquote> Those were the golden days! Reading mail! Today, every program attempts to determine the user's position and show flashy ads. Please welcome QtLocation and QtMultimedia. Tue, 17 Mar 2015 19:46:23 +0000