Qt 5.15 Released With Graphics Improvements, Preparations Ahead Of Qt 6

[DanL]

It's an LTS for paying consumers.

Maybe you missed this part?:

Qt 5.15 is available now for all our users. For our open source users, it will be supported in the same way as other regular Qt releases until the release of Qt 6. For commercial customers, Qt 5.15 will be long-term-supported (LTS) for three years with regular bug fix releases beyond the release of Qt 6.

[ZeroPointEnergy]

Google and Apple tried to share Webkit and it didn't work out. Turned out they had different priorities and didn't see eye to eye every time. Google ended up forking and is now using Blink.

But that does not explain why there is qtwebkit and gtkwebkit. Why don't they use one of the two libs and maintain their own fork?

[ssokolow]

That would require somebody to write and maintain one. Also you usually need different integrations. At least for WebKit it had different backends depending on what it integrated into, making each integration very unique. Chromium is more top down and could be reusably, if Google actually cared to maintain a reusable library, which they do not (also there is the debate over removing all the questionable call-home features of Chromium that Google does not like to have removed, but many others do).

Also, I don't know if they ported it to QWebEngine, but I know QtWebKit added an API the other integrations didn't offer, which allowed querying and manipulation of the DOM directly from C++ in a Selenium-like fashion, rather than by eval-ing snippets of JavaScript like the other integrations required.

[bug77]

Seriously, why has every UI framework their own webkit fork? Can't they depend on a common library?

Google and Apple tried to share Webkit and it didn't work out. Turned out they had different priorities and didn't see eye to eye every time. Google ended up forking and is now using Blink.

[carewolf]

Seriously, why has every UI framework their own webkit fork? Can't they depend on a common library?

That would require somebody to write and maintain one. Also you usually need different integrations. At least for WebKit it had different backends depending on what it integrated into, making each integration very unique. Chromium is more top down and could be reusably, if Google actually cared to maintain a reusable library, which they do not (also there is the debate over removing all the questionable call-home features of Chromium that Google does not like to have removed, but many others do).

[Setif]

It's an LTS for paying costumers.

[bug77]

Great!
Now I wish the Kubuntu develpers wold hurry up and update Qt 5.12 to Qt 5.15 and compile KDE Plasma 5.19 beta so we can test it and find bugs before the final release.

I loled so hard...

[miabrahams]

It took at least a year for Qt 5 to be stable enough to serve as a usable replacement. Get ready to use this one for a while.

[ZeroPointEnergy]

Seriously, why has every UI framework their own webkit fork? Can't they depend on a common library?

[carewolf]

my guess a lot of Distro's wont bother with 5.15 instead they'll wait for QT6

They will need both, but I doubt 6.0 will be that used. It will be somewhat incomplete.