[BiteCode_dev]

QT talent pool and ecosystem is a rounding error compared to what we have with the web ecosystem. If you want to make something with medias, graphs, a few custom widgets, a reactive layout and deep routing, it will take 10 to 30 times longer with QT.

I myself prefer the snapiness of QT apps, but budget and time to market will win.

[krageon]

Electron apps are always resource hogs, frequently slow and generally integrate extremely poorly. As a consumer I care not one whit for how large the "talent pool" for the web ecosystem is, I care about how terrible the application is.

As a developer I must say calling it talent is in most cases a huge stretch, as I do believe you can probably make something in Electron that performs passably, integrates passably and will still be a resource hog. The reason we see basically none of this is because people simply don't care to engineer these applications well. "It's just the browser", after all. Why look deeper?

[BiteCode_dev]

Sure but most teams do the maths for the cost/benefit ratio and make the call.

In this context the argument is moot: a better app that is too expensive or slow to make is simply not going to be released vs the worse one that actually gets published.

That's all there is to it.

That's why people still use wordpress, excel or jupyter notebooks for important stuff.

You may want things to be different, and for good reasons, but it's still what's the market has decided.

[anonymoushn]

What does "deep routing" mean?

[BiteCode_dev]

Views, sub views, partial views and complex hierachic workflows. Url base routers are great for those, but QT controllers let you reinvent the wheel.

[namibj]

I assume either deep nesting or deeplinks.