Is Qt for webassembly die?

tham

Haven't seem any update on Qt5.14 or Qt5.14.1, Qt company ditch qbs and make QWidget become obsolete already, and now Qt for WebAssembly do not looks like a project Qt company would like to put their resources into it since Qt5.14. Not only that, open sources users wouldn't be able to access LTS of Qt start from Qt5.15, more and more harder to convince the company to adopt Qt this day.

sierdzio

@tham said in Is Qt for webassembly die?:

make QWidget become obsolete already

Have you seen how many fixes and changes land for QWidgets with each new Qt version? Here's 5.14 as an example: changelog. The section for QtWidgets is quite big.

and now Qt for WebAssembly do not looks like a project Qt company would like to put their resources into it since Qt5.14

If I recall the news correctly, the team working on WASM was increased recently. How it is going along, though - I have no idea. You're right that blogs and changelogs for 5.14.x do not mention WASM much.

Not only that, open sources users wouldn't be able to access LTS of Qt start from Qt5.15

Incorrect. Qt 5.9 and 5.12 will continue being supported as LTS until their designated EOL dates. Also, 5.15 will see a few open source releases (5.15.1, 5.15.2 at least). All fixes will go into newer versions. Details are being discussed on the mailing list, perhaps 5.15 lifetime will be extended as it is the last release before Qt 6.

more and more harder to convince the company to adopt Qt this day.

Yeah, they're not making friends with their decisions :-)

tham

Have you seen how many fixes and changes land for QWidgets with each new Qt version? Here's 5.14 as an example: changelog. The section for QtWidgets is quite big.

Yes, but compare with qml, QWidget are obviously lack of love. Whatever, I prefer they don't add new features into QWidget but maintain after they adopt "features first, bug fix later" philosophy.

@sierdzio said in Is Qt for webassembly die?:

Yeah, they're not making friends with their decisions :-)

Yes, it is quite weird while other big players making their license become cheaper and easier to access, they are so eager to make their tools more famous, attract more developers, expand their community, but Qt company is going with reverse direction more and more.

Qt company still favor only expensive license. Their license for startup are not attractive at all, not only still expensive compare with other big players(ex : we can only develop but cannot distribute?).

The more you push away open source users, the less will know Qt. The less developers know Qt, the less investment the companies(potential customers) would like to put into Qt, and this could make the communities of Qt shrink. How could open source developers trust this tool when they trying so hard to push them away?

tham

@sierdzio said in Is Qt for webassembly die?:

Yeah, they're not making friends with their decisions :-)

Simply put, they are doing the same shit again--https://www.reddit.com/r/programming/comments/euopv6/qt_offering_changes_2020_mandatory_registration/

ODБOï

hi
@tham said in Is Qt for webassembly die?:

big players making their license become cheaper and easier to access

Can you please name some ?

You are free to switch to any other "big player" if you are so frustrated by Qt

tham

@LeLev said in Is Qt for webassembly die?:

Can you please name some ?

Microsoft now offers all its IDE+SDK free for opensource and "small business",
React Native and Other web technologies for "native" crossplataform development, with an ARMY of "cheap"JavaScript developers
Now Google with its Flutter thing
Unity gaining traction in the embedded market
Unreal engine also seeing how to milk the Tier 1 OEMs

Qt company did a lot of weird decisions these years(ex : no love for QWidget compare with qml, features first and bug fix later), I feel like they are losing the direction, trying to avoid backrupt and come up more and more bad ideas(ps : looks like 2015 is their last year to earn profit).

@LeLev said in Is Qt for webassembly die?:

You are free to switch to any other "big player" if you are so frustrated by Qt

Someday I may do it, but it is not there yet, maybe we could see a new fork of Qt of KDE in the future, this may happen if Qt company backrupt or the open source community do not trust this company anymore.

sierdzio

@tham said in Is Qt for webassembly die?:

Have you seen how many fixes and changes land for QWidgets with each new Qt version? Here's 5.14 as an example: changelog. The section for QtWidgets is quite big.

Yes, but compare with qml, QWidget are obviously lack of love. Whatever, I prefer they don't add new features into QWidget but maintain after they adopt "features first, bug fix later" philosophy.

Well, that's exactly what is happening to QtWidgets: they are maintained but not extended. Few new features, focus is on bug fixes. Widgets simply work, and they have worked since decades.

Their license for startup are not attractive at all

Depends. It's quite fine for me :-) Better than the old startup license (it's almost 50% cheaper now and includes more stuff).

[...] (ex : we can only develop but cannot distribute?).

This is not true for mobile, desktop, server applications. Only embedded uses requires some additional deal with Qt Company.

I'm not defending their decisions, I disagree with them too. But I don't want other people reading this to take away false impressions about the startup license.

lorn.potter

@sierdzio said in Is Qt for webassembly die?:

If I recall the news correctly, the team working on WASM was increased recently.

This is true! There are now two maintainers for wasm platform.

How it is going along, though - I have no idea. You're right that blogs and changelogs for 5.14.x do not
mention WASM much.

Work has been done getting QTcpSocket working, but it's not yet ready for prime time.

Look at the git log instead of the change log, as some wasm changes might not be big enough to enter into the change log.

tham

@sierdzio said in Is Qt for webassembly die?:

This is not true for mobile, desktop, server applications. Only embedded uses requires some additional deal with Qt Company.

Thanks for clarification, seems more reasonable. Whatever, their decisions are weird, super weird, while those big players trying to attract more developers, they push them away, not only that, they don't really care about the sound of developers. Here are the major issues of Qt they refuse to solve(collected from Qt blog)

Dumb license logic. It is so inelastic and it doesn't have enough options for a variety of businesses. Why do I pay for Qt Quick or Qt WebAssembly while only developing QtWidgets-based cross-platform desktop apps? It would be nice to have paying options based on Qt modules developers use. Also it would be nice to have a variety of license fees based on developer seats and revenue, not only 2 options but many options.
You are not paying enough attention to fixing bugs. There are bugs literally from BC. I think adding new features should not be your first priority, fixing bugs and maintaining stability should be.
Qt Widgets is totally abandoned for years (along with all the other Desktop support). Not enough modern and updated widgets there.
Not enough support and integration for common functionality on mobile platforms (like push notifications and other native functionality)
Android and IOS support is almost outdated. You are unable to keep up with the modern OS features (like android rounded icon support, battery state, signal strength, play store/app store integration, notifications, runtime permission requests etc (i.e. aab package support just added recently with 5.14, you are too slow)
You are pushing Automotive Suite, 3D stuff and 3D Design Studio etc too hard. All that Adobe Photoshop & AI, Sketch integrations etc. Why pushing hard on all those unnecessary stuff hard while not improving your Qt Modules and all the C++/QML code base? Qt is a C++/QML Framework, isn't it?
Qt Quick Controls 2: Not enough widgets there, also they are way too far from native look and feel. There is no proper desktop look & feel for Qt Quick Controls 2 also lacking IOS theme.
Qt Quick Designer is just a piece of garbage. I never found myself using it for developing UIs. It is too damn bad and unusable (also slow). It lacks tons of things like layout management, theming, different screen-dpi handling(this one I am not so sure, I don;t use it just because it is slow, early days it always crash or hang when I use it)

They tried so many things, develop so many new features, yet they refuse to hear the sound of developers, they should open a vote to collect the opinions of the programmers after so many years of failures to earn profit, they should know that Qt is a framework, a tool design for developers, not those business guys.

Developers are the one who really using and care about this library, this framework, not those business guys, the managers are totally incompetence if they still believe those business guys who don't know software(or don't have any passions of software) but money only.

ps : I would vote for bug fixes, focus on major platforms like desktop, mobiles, keep up with modern QS features, then enrich QWidget rather than support support more platforms, languages(python etc). Every platforms work but there are many features you have to develop again

J.Hilk

@tham said in Is Qt for webassembly die?:

runtime permission requests

those are part of the native Qt code base for at least a year, nearly 2

But I agree, the stuff you have to do to attach something to an E-Mail, or file sharing in general (A core feature of mobile apps) , are atrocious

lorn.potter

@tham said in Is Qt for webassembly die?:

@sierdzio said in Is Qt for webassembly die?:

You are not paying enough attention to fixing bugs. There are bugs literally from BC. I think adding new features should not be your first priority, fixing bugs and maintaining stability should be.

Hyperbole not withstanding, both features and bug fixes are ranked by developers/management on criticality.

Qt Widgets is totally abandoned for years (along with all the other Desktop support). Not enough modern and updated widgets there.

huh?
~/depot/qt/qt5/qtbase $ [5.15]> git log --pretty=oneline --no-merges --graph v5.14.0-alpha1...v5.14.1 src/widgets/

7a59d6f138ff8799170cc03d709525ab965d703a Doc: Correct non-link related qdoc compilation errors
99b396631999d7fc4e5e95b90a83858a5cb5a941 Doc: Add note about mac-specific behavior for setWindowIcon
9dcbf2cf5cbdfe35637ff323fd44729badaae811 QScrollBar: allow scrolling any scrollbar with any mouse wheel
1e42c97cf055ac20352d20150e2786c14565ea2b Bump copyright year
7b092b3fe3c9960a2e2866a3b03818fe63bbbac4 Remove clearWidgetPaletteHash argument from setPalette_helper
2a02487ff00341fcc07023b37ec527c2694fa4c1 Move tracking of widget specific app palettes to QApplicationPrivate
0c37bc11b5f379d442ed3475483d57449b63963d Share updates to QGuiApplicationPrivate::app_pal via helper function
22942058aa9c83acb809d0d4c6b78d29a3c33e12 Doc: Correct qdoc compilation errors qtbase
5af73cd9db52da287070cede300295b90f7ced67 Skip WA_DontShowOnScreen widgets when checking whether application can quit
78d2a04a01dbb989c017843f9d6d1f0c485c0e86 QSystemTrayIcon: Fix geometry() to work with scaling enabled
5b22d1719881b5f061be6b832a96a1e4305d981f Fix some issues of a clang-cl developer build
56674dca36f113369d3ed598192a392ceb723605 QSS/QComboBox: set correct palette when drawing SC_ComboBoxArrow
c62333424839b3229706a6ebb64ba271689a3b8c QPlainTextEdit: make sure firstVisibleBlock() is valid
240a8514f84e9be116acb34991b12a7aa2279914 Fix syncqt warning in qtestsupport_widgets.h
a6f56251ca6090cb0ba4c4989d7ccc638b1dbe2b Fix some qdoc warnings
4b1d370f755578f60bd9c73ca98eeb8e71463caf Check platformNativeInterface pointer before dereferencing
411c2e3e4f32ab98bab65bcd53faf11da3c4efd0 QCommonStyle: make sure to pass the widget to pixelMetric()
e0b9beb63dead017b6849ebcaa91c04a57f955c6 QFileInfoGatherer: don't pass empty list to QFileSystemWatcher
761025d08c32f3dddbd2d32f00b71f6411dd40ce Contain Qt::AA_SetPalette logic in QApplicationPrivate::setPalette_helper
c7ecff04609dd7d9282fa5de3d5d1e1fd189b4cb Simplify QApplication::palette
a132e0254005b2954b11705b32650c9018049187 Fix QAccessibleWidget::focusChild() to return focused descendant
0a09a6341ddff4397461deb98b8d7a28ca3c9dca Sync implementation of QGuiApplication and QApplication setPalette
04f5008f51dee9feec68afcee8cd8314b8e5ac62 Let sendApplicationPaletteChange() decide when it needs to exit early
df69364469c6816dab0f364f0687946a8d566679 Remove QApplicationPrivate::set_pal
da0e7457523a5c6867c2d9b9f0346167738f0323 Explicitly polish palette instead of relying on QApplication::setPalette
96d1d44279dc582355c21956fee99d945888fb07 Clean up QApplication::style default style construction
a9e628e7ec6b9d5bb38e64b7129c68320322033b Ensure override style properly clears out previous style if set
f6a2b81eabae81110f678263be8558c24072c458 Update system palette on application init if needed
6b06f12da6d5171d02764e9d6636c59731e2289f Unify system palette initialization during style change
14071b5a8e15b1f9ce0bf601a96ae365fa8983aa Clarify call to initializeWidgetFontHash in QApplication::setStyle
5a660353edde7b9f382ee41ecf278fc4537f38fa Doc: Fix qdoc compilation errors qtbase
382f1a221b353892844dc7b1495741c4669955e7 wasm: fix getOpenFileContent doc
e40e82ede1660e6467291002862732a536558f08 Add "checkable" state to accessible menu item
03dc30acca4976c716c723ff46d503d35459b2a0 Fix QPushButton style sheet style for overlay (content) image
c27123d7435e9451f3e44d9e823734e605279d0a QAbstractItemView: add a note about ToolTipRole in dataChanged()
46d21a3b34c2d252db14419a45957991acea949d QPushButton: fix icon + text layouting in RTL mode
baed8534bc1dac36a9d0ef4240fc14398076a192 Move the tooltip out of the way of very large mouse cursors
5272c35073aefee01751647dfb265aa3abf49823 Doc: Clarify ownership of added menu for QMenuBar::addMenu(QMenu *)
8339ce2155752eb8fa0f49f3fe4b24f9643ae463 Avoid crash in menu that was previously shown as submenu
009abcd7b66738bece6cf354776dfb2ef401636b QWidget: React to platform surface being created or destroyed
29adc0eed9b9dc3cce92f8acaaeaed3ab1bc6414 Fix updating the text cursor position after editing
ca7033935a26e2a11c7d872a6673e828eddf49ca Tell the truth about QDateTimeEdit's range-of-values properties
da94625f38692365217b4647dd721fa5ea14c6ff Fix sizeHint of QProgressDialog to have enough space for window margins
20266820a31d5cd4afc808bc8b3e9eb6e0396358 Item views: do not clip items horizontally in dragging icon
97ac281c1d70dcfbb137e5a83e24a747e9510116 QStyleSheetStyle: properly honor checkmark size when drawing a QMenu
925b33bdaabc7d07d6910d5696af1ff49287d8fa QPlainTextEdit: update internal palette on QEvent::EnabledChange
985f4910249a0308b746695e64aa1a6205492421 QTreeView: Reset the pressed index if the decoration was pressed on
4422a9bd88602c8dfde8648ad39692d968295cfc QWidget: don't set WA_PendingMoveEvent when geometry does not change
cd3585ab159c3d0614f418fd148b7cea77ea6d12 QDial: use correct button color
da0af1e21de6eda849dacf0283c78fbd36fd4f3f Doc: Improve explanation of QLineEdit input mask
54d5ca0c2766e915c960fa437cee6c20a324c1a7 Doc: improve Using Model Indexes in Model View Programming guide
9f48f1ebc21f783cd8bb7daab942d70aebf085bc QLineEdit: Fix End key for input masks
c15a069830baf87f57c84e86326cf86ba9a39713 QTreeView: make sure to not ask the old model during setModel
51cbd5288c85cb4de382cb23d6f5559c2b626126 Fix rendering of markdown in QLabel
aef07a433f16f5ed3800ee60e11116f78f13d3c4 QTableWidget: Fix -Wdeprecated-copy warning
f54e97726f36c56d9f51f2243493c55ab8cf7bef Doc: Add notes about Qt Style Sheets taking precedence
ccd3bf0871b81dfc09bb469b161f32dfb47ee53e Ensure that child windows are visible again when showing their parent
| * 88047be4ecb99799f4876ff3e7001abe34ac29bc QAbstractItemView: don't toggle selection on mouse move on some index
| * 0ae489053a9fafeb45f6de4431ed7b7ea992b8f8 Turn a local QHash into a QMultiHash
31a971f727ecf0c6651689f052b9fb4c67872b58 QColorDialog: Fix memory leak when picking screen colors
| * 5b22dc71a3eaa70fc2ae14ba950c8d897ef3cd6a QGraphicsItem: disable deprecated warnings during compilation
| * 265b25a5c36a938ca13c016a09caf9fb9384e408 Specify year in month name lookups for QCalendarWidget
| * 5edf34848a51c7678031aeb9576b8f3b7b5fceab QTableView: properly deselect row when column 0 is hidden/not visible
365f70be6ed53bf8b9ba7c5a78d5683e4ff8fe79 Doc: Correct snippet about customizing QMenuBar
31012df705c37503be00f0ddc2c323e73fd28067 Fix QGraphicsScene::update() performance
3dbc7596a3b7aca37e80f76288d3ab761ddd247a Drag'n'Drop: fix crash when widgets are destroyed during event handling
d2ae838a7c6a49eb826ddf8de115306d11dd4d30 Item views: fix regression causing unexpected widget overlapping
| * d71dbe3e9322430dceed9cb2d3f957fbac2ab715 docs: clarify usage of css 'qproperty' in stylesheets
| * 1b6db1849477be30ef0ca52c288d358b911ea1e4 Propagate application termination requests through QPA
| * e5c003b77ddd9830805124ab829067a7858bf024 Set icon on the select-all action in the text edit context menu too
| * 9cc040a806fd2e6f1458e801a99311168d594c77 Prepare for deprecating the QDesktopWidget
| * 95ac2072bbbcb50ff1f8b2fd9ffbcfb4e1326b27 QtWidgets: Suppress QEvent::WindowActivate when minimized
| * ffac8995769f27fe0d68d5e0cd75716afd3d1167 Fix the size calculation of QHeaderView when stylesheet is used
| * 66a9c4b0b259fe9a61150b7394af0f31ebfd38ac Remove usages of deprecated APIs of QDesktopWidget
| * 1748dc3e2d2367f9f01666212a22e6b1dde5dc89 QGroupBox: always disable children in a checkable, unchecked groupbox
| * 81a790969395feff73fa600908822765e97424e5 Fusion Style: Use high-dpi pixmaps
| * 65fcd8524da628c99e8cd28f983f0c17fbe157f0 QAbstractScrollArea: when used as a popup, apply regular popup behavior
| * f1dd6addda908185f497d299d706b88977dea858 Make QTextBlockFormat::MarkerType an enum class
b6ce61f486a06ded273d518d871906f9a53ab7c1 Fix text not rendering properly after setAlignment call
ce2fc51914f809369d5096e7a0621229dd9eaef9 Add check for global share context for QOpenGLWidget initialize
| * f7cb11d6f12f7bb353640637719292b95fd21438 QWidget: Answer question raised in fixme comment
| * 00e8f044e1954ea47f1f0c5c5ff35fff97b732be QWidget: document that a widget might only get a mouseDoubleClickEvent
5aa13ea144cff4dbadf12c08b7aa49646347e186 QTreeWidget: Don't assume the selected indexes include the first column
7d73d4b9a93b3132c1a24aa3ae77f0a307e821fd Remove the unregistered recognizer from the main list
e02293a76d21e7077f1952d4ed8af6c6d1970190 Always update the pressed position when pressing on an item
| * ad86c2f0abb4fab5bf871fe49b37e0a2f4a346bc Quiet several more warnings about QWheelEvent deprecations
947883141d9d8b3079a8a21981ad8a5ce3c4798e QWidget::setFocusProxy: adjust focus widget properly
8810f82f3f9b3fe35d82fb842a5a21a098b2343f QWizard/Aerostyle: Fix "&Next" shortcut
27782af8219e244fb8cea60e3f22448d5d075446 QWizard: Use member initialization in private classes
| * 688369999435d6f4755577fe47ff80132254bb26 QCommonStyle: Add SP_DialogNoButton case in standardIcon
| * 70c053ee684448984b1f762abd3b40884cece2fa QAbstractSpinBox css: properly honor spincontrol-disable-on-bounds
9b6179cf957c32e0c02547d510dfee2088f02340 Ensure all children of a widget get updated when a stylesheet changes

Not enough support and integration for common functionality on mobile platforms (like push notifications and other native functionality)

Android and IOS support is almost outdated. You are unable to keep up with the modern OS features (like android rounded icon support, battery state, signal strength, play store/app store integration, notifications, runtime permission requests etc (i.e. aab package support just added recently with 5.14, you are too slow)

Yes, Qt will always be behind developing mobile features because Qt does not own the platform.

You are pushing Automotive Suite, 3D stuff and 3D Design Studio etc too hard. All that Adobe Photoshop & AI, Sketch integrations etc. Why pushing hard on all those unnecessary stuff hard while not improving your Qt Modules and all the C++/QML code base? Qt is a C++/QML Framework, isn't it?

Qt Quick Controls 2: Not enough widgets there, also they are way too far from native look and feel. There is no proper desktop look & feel for Qt Quick Controls 2 also lacking IOS theme.

again, it's open source. patches welcome.

Developers are the one who really using and care about this library, this framework, not those business guys, the managers are totally incompetence if they still believe those business guys who don't know software(or don't have any passions of software) but money only.

'Those business guys' also care about the framework and demand features such as Photoshop integrations, etc because the customers demand them.

ps : I would vote for bug fixes, focus on major platforms like desktop, mobiles, keep up with modern QS features, then enrich QWidget rather than support support more platforms, languages(python etc). Every platforms work but there are many features you have to develop again

tham

@lorn-potter said in Is Qt for webassembly die?:

huh?
~/depot/qt/qt5/qtbase $ [5.15]> git log --pretty=oneline --no-merges --graph v5.14.0-alpha1...v5.14.1 src/widgets/

You should compare with the new features and changed with qml, QtQuick. Developers are not idiots, wouldn't deceived by cheap tricks like this. You expect a bunch of developers study mathematics, sciences, with master even phd degree deceived by tricks like this? Seriously?

Hyperbole not withstanding, both features and bug fixes are ranked by developers/management on criticality.

That is why your bugs become more and more.

again, it's open source. patches welcome.

it is a commercial project too. A commercial project which do not care about the voices of developers.

Those business guys' also care about the framework and demand features such as Photoshop integrations, etc because the customers demand them.

They care because they want more money, not because they want the tools become better. Economy situations of Qt company already shown us they are not professional and losing the heart of developers. Qt is a framework, a library design for developers, how could a commercial tool like this become profitable when the managers ignore voices of developers?

You are their employee, protect your employers are your responsible, but not mine. They are doing the same shit again--https://www.reddit.com/r/programming/comments/euopv6/qt_offering_changes_2020_mandatory_registration/, which pissed off lots of developers. I looking forward to the backrupt of this company.

lorn.potter

@tham said in Is Qt for webassembly die?:

@lorn-potter said in Is Qt for webassembly die?:

huh?
~/depot/qt/qt5/qtbase $ [5.15]> git log --pretty=oneline --no-merges --graph v5.14.0-alpha1...v5.14.1 src/widgets/

You should compare with the new features and changed with qml, QtQuick. Developers are not idiots, wouldn't deceived by cheap tricks like this. You expect a bunch of developers study mathematics, sciences, with master even phd degree deceived by tricks like this? Seriously?

What trick? I offered proof that widgets are in fact, being worked on.

Hyperbole not withstanding, both features and bug fixes are ranked by developers/management on criticality.

That is why your bugs become more and more.

umm. no. All software has bugs. Complicated software often has complicated bugs.

again, it's open source. patches welcome.

it is a commercial project too. A commercial project which do not care about the voices of developers.

ermm.. the project is made up of developers... not just ones that work for Qt Company.

Actually, if you have a commercial license, then you have direct access to the support crew.

You are their employee, protect your employers are your responsible, but not mine. They are doing the same shit again--https://www.reddit.com/r/programming/comments/euopv6/qt_offering_changes_2020_mandatory_registration/, which pissed off lots of developers. I looking forward to the backrupt of this company.

I am not an employee of Qt Company, I live no where near a Qt Company office and I haven't set foot in one for better part of a decade. I used to work for Nokia though.

Having to register an account for the convenience of getting to download ready made binaries, when the source code is available to use is hardly a good reason to be mad, IMHO. I dunno, seemed much ado about nothing.

tham

@lorn-potter said in Is Qt for webassembly die?:

Having to register an account for the convenience of getting to download ready made binaries, when the source code is available to use is hardly a good reason to be mad, IMHO. I dunno, seemed much ado about nothing.

Your eyes are blinded, many developers got pissed off by this stupid decisions. They cancel this action in 2015 because many developers don't like it, today they do it again, for me, this sound like the company is going to bankrupt soon, that is why they are so desperately to collect data of the users in order to sell the company with higher prices. Don't forget this company do not earn a penny in last few years. I repeat, how could a framework develop to ease the pain of developers sells well when the managers of the company are so damn arrogant, refuse to listen to the voices, the real need of the developers? They should fail.

What trick? I offered proof that widgets are in fact, being worked on.

I am not an idiot, other developers not idiots either. We all know Qt company do not intent to put much efforts into QWidget long time ago, compare with qml and QtQuick. It is still maintaining and sometimes with some small features added, that is all.

You know what I am trying to talk, stop your trick, unless you are trying to fool idiots.

jsulm

@tham Please stop talking this way!
We want to have a forum with civilised discussions.
Read https://forum.qt.io/topic/113070/qt-code-of-conduct

Also, this is user forum, if you want to discuss this topic with QtCompany then please contact the company.

tham

This post is deleted!

tham

@jsulm said in Is Qt for webassembly die?:

Also, this is user forum, if you want to discuss this topic with QtCompany then please contact the company.

Hahahaha, you think those arrogant managers really care about the feeling of developers? They only care about money, and trying their best to kill Qt, now KDE already infected by the "virus" spread by Qt company.

They will erase the posts they don't like, just check out this page. This company deserve to die, the sooner the better.

sierdzio

@tham said in Is Qt for webassembly die?:

@jsulm said in Is Qt for webassembly die?:

Also, this is user forum, if you want to discuss this topic with QtCompany then please contact the company.

Hahahaha, you think those arrogant managers really care about the feeling of developers? They only care about money, and trying their best to kill Qt, now KDE already infected by the "virus" spread by Qt company.

They will erase the posts they don't like, just check out this page. This company deserve to die, the sooner the better.

They don't do it on this forum at least, that I can assure you of.

We all know Qt company do not intent to put much efforts into QWidget long time ago, compare with qml and QtQuick. It is still maintaining and sometimes with some small features added, that is all.

Yes that even described in official module statuses: QtWidgets module is done. It only receives small updates and bug fixes - but there are no plans to deprecate or remove it. And besides, amount of "efforts" put into QML is not that big nowadays. Check out the changelogs, it's mostly bug fixes and small additions.

Anyway, your question was about future of Qt WebAssembly, and Lorn has answered that it's not dying. It may not be receiving enough attention in your view (in mine too), but it's not getting deprecated.

tham

@sierdzio said in Is Qt for webassembly die?:

Anyway, your question was about future of Qt WebAssembly, and Lorn has answered that it's not dying. It may not be receiving enough attention in your view (in mine too), but it's not getting deprecated.

Ok, I knew this already, just get upset by the lie, if Qt company don't stop their nonsense, a fork of Qt may happen, and I will be happy to contribute to the project if that really happen. TQtC deserve to die, the sooner the better

lorn.potter

@tham said in Is Qt for webassembly die?:

Ok, I knew this already, just get upset by the lie, if Qt company don't stop their nonsense, a fork of Qt may happen, and I will be happy to contribute to the project if that really happen. TQtC deserve to die, the sooner the better

No one has lied to you. If you do not like using Qt, then go away and stop trolling here.