Live data from Hacker News

Electron Fiddle: Get started with Electron

electronjs.org

11–20 of 104 posts

Re: Electron Fiddle: Get started with Electron

#12
post #2

Honest question, when solutions like https://github.com/tauri-apps/tauri exist out there that promise smaller build sizes and similar developer experiences, are folks still using Electron to build new apps?

A reason to keep using Electron rather than Tauri is when you need to make sure the UI is going to be displayed the same way on each platform.

Tauri uses the OS's native webview which means that there can be differences in how the DOM is displayed. It's not the same browser engine being used for each platform.

Re: Electron Fiddle: Get started with Electron

#13
What exactly makes the average Electron program so goddamn awful? Does the Javascript language inherently result in a bloat runtime? Are the runtimes accidentally bloat? Is it all the browser stuff and not the JS runtime per se? Or maybe just bad programming on the dev side?

Re: Electron Fiddle: Get started with Electron

#14
post #13

What exactly makes the average Electron program so goddamn awful? Does the Javascript language inherently result in a bloat runtime? Are the runtimes accidentally bloat? Is it all the browser stuff and not the JS runtime per se? Or maybe just bad programming on the dev side?

its a massive embedded browser. imagine if every app you opened on your computer was a separate process running chrome? thats more or less literally what electron is.

Re: Electron Fiddle: Get started with Electron

#15
Please can Electron die already? Almost every Electron program I use could be a PWA. Slack has no reason to need another browser engine running. You could make a point for native integration, but there is none. And all it does is display text (and images). What a world we live in. Worse is better, amirite?

Re: Electron Fiddle: Get started with Electron

#16
I struggled between Flutter and Electronjs, checked at Tauri too.

Electronjs does the 3 Desktops (linux,windows,macos).

Tuari is new, serves the same user base, smaller, but you need learn Rust.

Flutter does 3 Desktops and 2 Mobile platforms(android,ios), but you need learn Dart.

While doing my own research, I eventually chose Flutter, reasons are:

    * it does 5 platforms fairly well
    * its user base keeps rising rapidly over recent years
    * dart is very much java|c++|javascript syntax alike, just simpler, picking up dart at least is much easier for me comparing to Rust.

Re: Electron Fiddle: Get started with Electron

#17
post #13

What exactly makes the average Electron program so goddamn awful? Does the Javascript language inherently result in a bloat runtime? Are the runtimes accidentally bloat? Is it all the browser stuff and not the JS runtime per se? Or maybe just bad programming on the dev side?

its a massive embedded browser. imagine if every app you opened on your computer was a separate process running chrome? thats more or less literally what electron is.

That’s just what opening a new tab in your web browser is.

Dedicated Electron-based apps are even worse than that: a separate set of processes running their own embedded version of Chrome.

Re: Electron Fiddle: Get started with Electron

#18
post #15

Please can Electron die already? Almost every Electron program I use could be a PWA. Slack has no reason to need another browser engine running. You could make a point for native integration, but there is none. And all it does is display text (and images). What a world we live in. Worse is better, amirite?

[deleted]

Re: Electron Fiddle: Get started with Electron

#19
post #2

Honest question, when solutions like https://github.com/tauri-apps/tauri exist out there that promise smaller build sizes and similar developer experiences, are folks still using Electron to build new apps?

I’ll reply to your question with a question: once VSCode has proved one could build hyperscale complex apps that perform well, would you be fast to bet for less proven tech?

I’ve had a great experience using VSCode on occasion (I’m a JetBrains guy), and loads of other people, including some great programmers, rave about it. I’ve similarly had a fairly solid experience with Spotify desktop across different platforms.

I’m asking genuinely, is it such a subpar choice when there’s such proven success cases?

Re: Electron Fiddle: Get started with Electron

#20
post #13

What exactly makes the average Electron program so goddamn awful? Does the Javascript language inherently result in a bloat runtime? Are the runtimes accidentally bloat? Is it all the browser stuff and not the JS runtime per se? Or maybe just bad programming on the dev side?

“Does the Javascript language inherently result in a bloat runtime?“

No

“Are the runtimes accidentally bloat?”

Not accidentally

“Is it all the browser stuff and not the JS runtime per se?”

Basically, yes

“Or maybe just bad programming on the dev side?”

No

Essentially the reason Electron apps are so heavy is they run on a browser, not on an operating system.

In the beginning, programs ran directly on hardware, and things were good. (e.g. Pretty much every game would ship with a custom bootloader that knew how to address the hardware and exposed this to the program, you didn’t - couldn’t - have anything else running at the same time.)

Later on, programs ran on the operating system, and things were okay. Operating systems abstracted over all the possible hardware configurations in an acceptable way and users got the benefit of running multiple programs simultaneously without too much of a performance cost.

Now, programs run on the browser, itself a program running on the operating system. Because the browser wants to be a platform for any other program, it has to hook into almost every part of the operating system, so that it can support almost any program. This necessarily brings with it enormous bloat - in effect you’re running one general-purpose pseudo-OS framework per program.

At places I’ve worked there have been discussions about whether to use Electron. Something one dissenter said has stuck with me. “Imagine every Python module you imported ran in its own Docker container. You would quit, but that’s what we’re asking of users.”

Post reply on HN