Re:You probably don't need a single-page app
by AnIdiotOnTheNet on Sunday February 17, 2019 @10:51AM
(#19184994)
> I can spot Qt a mile away. A lot of the visuals look wrong and a lot of the controls don't behave right.
You mean it has no respect for your native toolkit... just like the web?
Re:You probably don't need a single-page app
by tyingq on Sunday February 17, 2019 @11:47AM
(#19185326)
"just like the web"
How true is that? I was under the impression that for Android and iOS, Chrome used the native widgets for most things.
Re:You probably don't need a single-page app
by tedunangst on Sunday February 17, 2019 @01:49PM
(#19186064)
How many SPAs use native controls with minimal styling?
As a user, I usually can't even tell when they're using a polyfill on the web (except when they stop, like GitHub did with type=date). (As a developer, I often can't tell the difference, either. Some of them are that good!) So long as you generate HTML/CSS/JS, it doesn't matter to me how you do it. That's as 'native' to the web as you can get.
I can spot Qt a mile away. A lot of the visuals look wrong and a lot of the controls don't behave right. It's frustrating to use, and I always slow way down and double-check my work because, e.g., popup menus show the 'accept' animation even when you cancel them.