News for hackers. Stuff that matters.

A comment on Going native. Parent comment

Re:Going native by josephg on Thursday March 23, 2017 @07:33PM (#13945331)
That just makes the platform native, which doesn't say anything at all. Presumably the app itself is still written in javascript, so its not native at all - its just bundling its own (native) copy of chrome.
[ Parent | on HN ]
Re:Going native by colordrops on Friday March 24, 2017 @01:05AM (#13946740)
So are you saying anything with a runtime is not native, even if embedded in an executable? Is a go app native?
[ Parent | on HN ]
Re:Going native by meditationapp on Friday March 24, 2017 @02:10AM (#13947032)
Does a go app use the native toolkit?

QT isn't native either.

[ Parent | on HN ]
Re:Going native by danieldk on Friday March 24, 2017 @02:49AM (#13947164)
Actually, Qt (as in Qt Widgets) is a peculiar case. Qt draws its own widgets, but on some platforms uses native theming APIs to draw widgets (e.g. HITheme in macOS[1]). Though they are apparently experimenting with native widgets now [2].

So I'd say Qt is more native than e.g. Electron, but it is definitely not completely native. Except on Linux of course.

[1] http://doc.qt.io/qt-4.8/qmacstyle.html#details

[2] http://blog.qt.io/blog/2017/02/06/native-look-feel/

[ Parent | on HN ]