News for hackers. Stuff that matters.
Re:Ask HN: Is there still a place for native desktop apps? by avmich on Sunday May 17, 2020 @06:19PM (#23216020)
Do you count Qt apps as native, but not count web apps as native? Why?
Re:Ask HN: Is there still a place for native desktop apps? by AsyncAwait on Sunday May 17, 2020 @06:22PM (#23216042)
Qt may not 'look' native, but it has native performance, whereas Electron really doesn't.
Re:Ask HN: Is there still a place for native desktop apps? by userbinator on Sunday May 17, 2020 @08:08PM (#23216763)
The difference between "Qt native" and "native native" (e.g. Win32 or Cocoa) is still noticeable if you pay attention, although it's not quite as obvious as between Electron and the former.

(Likewise, applications using the JVM may also look very convincingly like native ones, but you will feel it as soon as you start interacting with them.)

Re:Ask HN: Is there still a place for native desktop apps? by nv-vn on Monday May 18, 2020 @12:37AM (#23218408)
Is it really even worth highlighting though? I use Telegram Desktop (Qt) daily and it is always, 100% of the time completely responsive. It launches basically instantly the second I click the icon and the UI never hangs or lags behind input to a noticeable degree. If we transitioned to a world where everyone was writing Qt instead of Electron apps we would already have a huge win.
Re:Ask HN: Is there still a place for native desktop apps? by catblast on Monday May 18, 2020 @10:38PM (#23230794)
If you're using KDE, Qt is "native native".

You're fundamentally mistaken about where Qt sits in the stack - it effectively sits in the same place as USER32/WinForms in Windows or NS/Cocoa GUI widgets of OSX. It is reasonable to think of it as an alternative native GUI library in that sense. If it is slower, it's because an implementation of something is slower, not because of where it lives or an abstraction cost.

Qt pretty much draws using low-level drawing APIs on the respective platform. And although Qt itself is not written in the most performance sensitive C++, it is still orders of magnitude faster than most (and it's not like Chrome doesn't pay overhead) - people rag on vtable dispatch speed but jeez its still orders of magnitude faster than something like ObjC which served Apple quite well for years.

The performance of a Qt app is more likely a function of the app itself and how the app developers wrote it.

But no, you're not noticing any micro-seconds differences in C++ overhead for Qt over "native native" - and you're basically comparing the GUI code of the platform - since Qt does it's own rendering. Win32 is mostly pretty good, NS is a mixed bag, and Gtk+ is basically a slug. In all cases there is some kind of dynamic dispatch going on, because that is a fundamental pattern of most GUI libraries. But dynamic dispatch is almost never a factor in GUI render performance. Things like recalculating sizes for 1 million items in a table on every repaint are the things that get people into trouble, and that is regardless of GUI library.

Re:Ask HN: Is there still a place for native desktop apps? by outside1234 on Sunday May 17, 2020 @07:21PM (#23216460)
VSCode is indistinguishable from native, so not sure its Electron that's at fault here.
Re:Ask HN: Is there still a place for native desktop apps? by keb_ on Sunday May 17, 2020 @08:22PM (#23216845)
This gets said a lot, and granted VSCode is certainly one of the best performing Electron apps, but it definitely is not indistinguishable from native apps. Sublime, Notepad++, or TextAdept all fly compared to VSCode in terms of performance and RAM efficiency.
Re:Ask HN: Is there still a place for native desktop apps? by fiddlerwoaroof on Sunday May 17, 2020 @09:39PM (#23217301)
On Mac, VSCode does a better job than many apps at emulating the Cocoa text input systems but, like every electron app, it misses some of the obscure corners of cocoa text input system that I use frequently.

If we’re going to use JavaScript to write native apps, I’d really like to see things like React Native take off: with a good set of components implemented, it would be a first class environment.

Re:Ask HN: Is there still a place for native desktop apps? by AlchemistCamp on Sunday May 17, 2020 @07:32PM (#23216543)
No. I like VS Code but it's a hog.

I still use Macvim or even Sublime Text a lot for speed reasons, especially on large files.

Re:Ask HN: Is there still a place for native desktop apps? by andai on Sunday May 17, 2020 @07:31PM (#23216525)
If your native apps are indistinguishable from VSCode, they're doing something wrong.
Re:Ask HN: Is there still a place for native desktop apps? by voltagex_ on Sunday May 17, 2020 @08:16PM (#23216803)
Start Notepad++ or https://github.com/rxi/lite and then compare the startup speed with VSCode.
Re:Ask HN: Is there still a place for native desktop apps? by drngdds on Sunday May 17, 2020 @08:22PM (#23216843)
I use VS Code daily (because it seems to be the only full-featured editor that Just Works(TM) with WSL), but it can get pretty sluggish, especially with the Vim plugin.
Re:Ask HN: Is there still a place for native desktop apps? by dep_b on Monday May 18, 2020 @03:52AM (#23219548)
Try to use AppleScript or Accessibility. It's like VS Code doesn't even exists.
Re:Ask HN: Is there still a place for native desktop apps? by eyegor on Sunday May 17, 2020 @10:16PM (#23217522)
If I recall correctly, Microsoft forked their own version of electron to make vs code feel more snappy. Because normal electron runs like slack.
Re:Ask HN: Is there still a place for native desktop apps? by RMPR on Tuesday May 19, 2020 @05:10AM (#23232865)
I don't think so, Microsoft wanted to fork electron in the past to replace Chromium with edgeHTML, but it didn't happen. VSCode is powered by Monaco Editor github.com/microsoft/monaco-editor, and VSCode feels snappier than let's say Atom, probably because of Typescript.
Re:Ask HN: Is there still a place for native desktop apps? by meritt on Sunday May 17, 2020 @11:55PM (#23218158)
Try opening a moderately large (even 2MB) .json file in VSCode, and then do the same in sublime.

VSCode very quickly freezes because it cannot handle a file that size. Sublime not only opens it but syntax highlights immediately.

Re:Ask HN: Is there still a place for native desktop apps? by inapis on Monday May 18, 2020 @04:33AM (#23219856)
This is something with your configuration. OOB VSCode will immediately show you the file but disable tokenization and certain other features. I regularly open JSON files upto 10 MB in size without any problem. You probably have plugins which impede this process.
Re:Ask HN: Is there still a place for native desktop apps? by thawaway1837 on Sunday May 17, 2020 @06:54PM (#23216282)
Isn’t that more of an Electron issue?

I mean, is anyone clamouring for VS Code, for example, to be rewritten in native toolkits?

Re:Ask HN: Is there still a place for native desktop apps? by madeofpalk on Sunday May 17, 2020 @07:32PM (#23216542)
I would argue that the web platform is one of the most optimised and performant platforms for apps.
Re:Ask HN: Is there still a place for native desktop apps? by wolco on Sunday May 17, 2020 @08:03PM (#23216742)
When you say web platform do you mean a browser? Using a browser is the mosted optimised and performant over installing an application on your desktop?

Curious what desktop do you run your browser under?

I would give you an example of a simple video split application. A web platform requires uploading, downloading and slow processing. A local app would be hours quicker as the data is local.

Re:Ask HN: Is there still a place for native desktop apps? by cglong on Sunday May 17, 2020 @09:21PM (#23217210)
No reason a video splitting app couldn't be written with client-side JS.
Re:Ask HN: Is there still a place for native desktop apps? by saagarjha on Monday May 18, 2020 @06:21AM (#23220567)
That sounds like it’d probably be slow.
Re:Ask HN: Is there still a place for native desktop apps? by boomlinde on Monday May 18, 2020 @06:39AM (#23220698)
So please do.
Re:Ask HN: Is there still a place for native desktop apps? by jcelerier on Sunday May 17, 2020 @06:31PM (#23216116)
a few reasons :

- Qt is actually the native toolkit of multiple operating systems (Jolla for instance and KDE Plasma) - you just need to have a Linux kernel running and it handles the rest. It also does the effort of going to look for the user theme for widgets to mix in with the rest of the platform, while web apps completely disregard that.

- Windows has at least 4 different UI toolkits now which all render kinda differently (win32, winforms, wpf, the upcoming winui, whatever is using Office) - only Win32 is the native one in the original sense of the term (that is, rendering of some stuff was originally done in-kernel for more performance). So it does not really matter on that platform I believe. Mac sure is more consistent, but even then ... most of the apps I use on a mac aren't cocoa apps.

- The useful distinction for me (more than native and non-native) is, if you handle a mouse event, how many layers of deciphering and translation has it to go through, and are these layers in native code (eg. compiled to asm). As it reliably means that user interaction will have much less latency than if you have to go through interpreted code, GC, ...

Of course you can make Qt look deliberately non-native if you want, but by default it tries its best - see https://code.woboq.org/qt5/qtbase/src/plugins/platforms/coco... and code such as https://code.woboq.org/qt5/qtbase/src/plugins/platforms/wind...

Re:Ask HN: Is there still a place for native desktop apps? by irishcoffee on Sunday May 17, 2020 @07:20PM (#23216453)
Knowing what I know about Qt and what I've done with it in my day job, it's basically the best kept secret on hn. What they're doing with 6+licensing... I'm not sure how I feel, but from a pure multi-platform framework it really is the bees knees.

I've taken c++ qt desktop apps that never had any intention of running on a phone, built them, ran them, everything "just worked. I was impressed.

Re:Ask HN: Is there still a place for native desktop apps? by hoseja on Monday May 18, 2020 @03:28AM (#23219376)
I just wish it weren't stuck, anisotropically, ~10 years in the past. Maybe Qt6 will be better, but more likely it will be more and more QML.
Re:Ask HN: Is there still a place for native desktop apps? by RMPR on Tuesday May 19, 2020 @05:14AM (#23232879)
Since QML uses Javascript it may be their best bet to attract new developers.
Re:Ask HN: Is there still a place for native desktop apps? by hoseja on Tuesday May 19, 2020 @08:07AM (#23233923)
Yes, well, QML also uses JavaScript.
Re:Ask HN: Is there still a place for native desktop apps? by PaulDavisThe1st on Sunday May 17, 2020 @07:01PM (#23216337)
This is not really accurate. Qt relies on a lower level windowing system (X Window, Wayland, Cocoa, win32 etc. etc.).

Also worth noting that many creation-centric applications for the desktop (graphics, audio, video etc. etc.) don't look "native" even when they actually are. In one case (Logic Pro, from Apple), the "platform leading app from the platform creator" doesn't even look native!

Re:Ask HN: Is there still a place for native desktop apps? by jcelerier on Sunday May 17, 2020 @07:36PM (#23216568)
> This is not really accurate. Qt relies on a lower level windowing system (X Window, Wayland, Cocoa, win32 etc. etc.).

Qt also supports rendering directly on the GPU (or with software rendering on the framebuffer) without any windowing system such as X11 or Wayland - that's likely how it is most commonly used in the wild, as that's one of the main way to use it on embedded devices.

Re:Ask HN: Is there still a place for native desktop apps? by PaulDavisThe1st on Sunday May 17, 2020 @08:49PM (#23217024)
I'd like to see it do that on macOS ...

You're seriously suggesting that the common use of Qt on Linux systems is direct rendering without the windowing system?

Re:Ask HN: Is there still a place for native desktop apps? by gwillz on Sunday May 17, 2020 @09:06PM (#23217116)
Not parent, but yes, sort of.

Arguably it's use in embedded contexts is much larger than desktop. It's quite popular for in-car computers, defense systems, etc.

For desktop linux, yes, it uses the windowing system.

Re:Ask HN: Is there still a place for native desktop apps? by jcelerier on Monday May 18, 2020 @03:31AM (#23219392)
Well, yes. I can't tell too much because of NDAs but if you go buy a recent car there is a good chance that all the screens are rendered with Qt on Linux or a RTOS - there is likely more of those than desktop linux users as much as this saddens me
Re:Ask HN: Is there still a place for native desktop apps? by saagarjha on Monday May 18, 2020 @06:23AM (#23220587)
On macOS Qt doesn’t really use Cocoa, it use Quartz/CoreGraphics (the drawing rather than the application layer). Note that Apple’s pro apps are native controls with a UI theme: they usually behave like their unthemed counterparts.
Re:Ask HN: Is there still a place for native desktop apps? by PaulDavisThe1st on Wednesday May 20, 2020 @12:54AM (#23243406)
I had meant to write Quartz, not Cocoa.

I know how Qt works at that level. I did a bunch of work in the mid-naughts on the equivalent stuff in GTK.

Re:Ask HN: Is there still a place for native desktop apps? by rattray on Sunday May 17, 2020 @07:31PM (#23216531)
> Qt relies on a lower level windowing system

That's true of QtWidgets, but not QML / Qt Quick (the newer tool), correct? (I found this hard to determine online).

Re:Ask HN: Is there still a place for native desktop apps? by jcelerier on Sunday May 17, 2020 @08:01PM (#23216728)
Kinda - QML is a programming language, Qt Quick is an UI scene graph (with the main way to use it being through QML) which also "renders everything" and makes by default less effort than widgets to look like the OS.

But :

- QML can be used with other graphics stack - for instance Qt Widgets like with https://www.kdab.com/declarative-widgets/ or alternatives to the official Qt Quick controls with https://github.com/uwerat/qskinny or with completely custom rendering like here with NanoVG : https://github.com/QUItCoding/qnanopainter

- QtQuick Controls can be made to use the same style hints than the desktop with https://github.com/KDE/qqc2-desktop-style

Re:Ask HN: Is there still a place for native desktop apps? by madeofpalk on Sunday May 17, 2020 @07:36PM (#23216561)
What does “native” even mean?

Put a <button/> in an HTML page and you get a platform-provided UI widget.

Re:Ask HN: Is there still a place for native desktop apps? by PaulDavisThe1st on Sunday May 17, 2020 @08:51PM (#23217035)
It's not platform-provided in my experience, but browser provided. The result of <button/> when viewed in a browser on macOS has no relation to the Cocoa API in any meaningful sense.
Re:Ask HN: Is there still a place for native desktop apps? by madeofpalk on Sunday May 17, 2020 @09:39PM (#23217300)
I'm pretty sure that when you render just a <button> in at least Safari, the browser will render a native Cocoa button control. If you set a CSS property like background colour or change the border, then it will "fall back" to a custom rendered control that isn't from the OS UI.

I did a small bit of research into this, and found plenty of "anecdotal" evidence, but nothing confirming for sure. I'm looking and interacting with the controls and they seem pretty native - if they're a recreation than that's pretty impressive :)

Re:Ask HN: Is there still a place for native desktop apps? by saagarjha on Monday May 18, 2020 @06:24AM (#23220595)
The drawing is native and the interaction is handled by the browser.
Re:Ask HN: Is there still a place for native desktop apps? by slightwinder on Monday May 18, 2020 @05:29AM (#23220241)
A GUI is a collection of elements with specific look and behaviour. A Desktop Environment is a collection of GUI(s), tools and services. Native means you have something which follows this look and behaviour 100% and can utilize all the tools and services.

Implementing the look is simple, adding behaviour quite harder and utilizing the service the endgame. WebUI usually does nothing from those or some parts, it all depends on the constellation. But usually there is a obvious difference at some point where you realize whether something is native or just made an attempt.