Re:Sunsetting Atom
by munificent on Wednesday June 08, 2022 @01:19PM
(#31670719)
"Native UI" can be interpreted to mean "UI written in native (i.e compiled to machine) code" or "UI written using the OS's native widgets". You are presuming that the only correct definition is the latter, but it's pretty clear from context that they mean the former.
[ Parent
| on HN ]
Yes, you can argue for another plausible interpretation of those two words, but in actual usage "Native UI" has always meant the platform's native UI framework.
A lot of people started to refer to Qt as native around Electron's time. The only place where Qt is native as such in on a KDE Plasma/LxQt desktop.
You're correct, although Qt attempts to do fake native widgets on Win / Mac, and given how relatively lightweight it is compared to Electron, it's understandable how it became a obviously point of contrast with the latter, which doesn't even pretend to be native. Given a choice between the two I will obviously take fake native widgets over nothing.
Re:Sunsetting Atom
by mwcampbell on Thursday June 09, 2022 @05:52AM
(#31679325)
I, on the other hand, will take whichever widgets have the better accessibility implementation. Currently Electron beats Qt on this.
Re:Sunsetting Atom
by BaseballPhysics on Wednesday June 08, 2022 @03:43PM
(#31672946)
> but it's pretty clear from context that they mean the former
It absolutely was not clear, which is why I checked the website and then pointed out the lack of clarity.
At first my thought was "Wow, nice, another UI toolkit that uses native widgets, that's good!" But, alas, it was not to be.