Hacker News Reader

Comment by appimonster | Hacker News Reader

Sounds great! Now, We can make memory efficient Electron with this kind of runtime. It will make JavaScript to be used in creating desktop application more reasonable.

View on HN

Not really, multithreaded applications are not more memory-efficient.

Yes in common sense.

But for node cluster's case, if we need to load a data set for a worker to serve request, it has to be loaded on each process. While the multi-threaded model will have only one copy.

There are many, many tools for creating great desktop applications. Why would using JavaScript for this ever be reasonable?

To share the same codebase across Windows, macOS, linux, browser

So, instead of writing great multiplatform desktop app in, say, Qt, and writing great Web frontend, you write half-baked desktop-web hybrid that doesn't feel great anywhere. Awesome.

Atom and VS Code don't "feel great"? Yes, there are lots of shitty Electron apps out there, but don't the good ones prove that it's possible to write good ones too?

I would throw GitKracken in the pot, with apps done well using Electron.

I'm with you here. Electron has gotten a bad name thanks to resource hogs like Slack, but it can also be used to create amazing multi-platfotm desktop apps. VS Code is a great example of Electron done right - compared to the full VS it absolutely flies, while still being packed with features and being very extensible.

Do you run Slack on Windows by chance? I've only seen it being CPU intensive twice on macOS.

I haven't tried VS Code, but Atom definitely doesn't feel that great. Looks like a lightweight editor, feels like a big, heavy moloch.

Atom's selling point to me was always its easy hackability, and that's where Electron tremendously wins: doing hacks, software meant to be set up quick'n'dirty, personal experiments, stuff done because "why not". I'm glad that Electron (and Atom too) exists because of that. However, that's definitely not a reason to write any serious tools in it. Using any Electron app with my 8GB RAM is a nightmare, and most of them look so out of place that (from the UX perspective) I don't know why they were put outside of the browser in the first place.

[eidt] Oh, and the main thing - VS Code and Atom definitely don't share their code with any Web version running in browser. Doesn't that make the original argument moot?

vscode does share code with the browser-based editor used in MSFT sites like VS Team Services and onedrive. It was actually first released there as a browser-based editor before being adapted for use in a standalone desktop application.

QT doesn't feel great anywhere either (except Linux, and there only because the UI standards are "whatever goes").

At least it's fast.

Whats wrong with QT on other platforms? If it is about the looks, it looked pretty good on Windows as far as i remember, as for speed, it is mostly down to the developer not the language.

The problem is the "pretty good" uncanny valley.

I wouldn't write something in QT nowadays, mostly for shallow reasons.. it just feels silly to have that bubbly interface running on anything past Win XP.

What "bubbly interface"? The Qt apps I'm aware of on my Win10 system look just as flat as everything native.

EDIT: found one that doesn't, but it clearly loads some weird custom stylesheets, since it doesn't look like anything else.

Cos by using JS you don't need low level knowledge of how computers work and you don't have to plan too far in advance. People are not big fans of learning, specially the things they deem arcane.

That's a great reason for Electron to exist and I'm all for it. If you want to mess around, do silly stuff just because you can, it's amazing that such technologies exist and you can do magic with pretty low learning curve. Heck, I've been doing stuff in the past like complete smartphone UI with Node and Chromium, just because I could and wanted to experiment.

However, that's a really bad argument when it comes to software development of proper tools that need to be developed and maintained and actually used by people.

Yeah, it was more tongue in cheek argument, but sadly i feel like it is truth.

In-browser is probably a bit of a stretch, but add mobile (also possible with JavaScript) while keeping performance for cross-platform GUIs:

Why I use Object Pascal | https://news.ycombinator.com/item?id=15490345 (Oct 2017,250+points,215+comments)

http://www.lazarus-ide.org/

Reply on news.ycombinator.com