People that are upset about electron should consider it’s not:
Electron App vs Wonderful Fully Supported Native Linux Application
The reality is that your choice is largely:
Electron App vs No App (maybe running their windows app in wine if you can get that to work)
It’s not like companies are going to go build a native linux app but electron got in their way. It was always electron or no support.
So if you like the app, remember that the ram and the cpu you paid for doesn’t provide value unless it’s doing something. There’s no trophy you get at the end of your life for “most cumulative ram left idle”
So if you like the app, remember that the ram and the cpu you paid for doesn’t provide value unless it’s doing something. There’s no trophy you get at the end of your life for “most cumulative ram left idle”
Honestly even with more than 1 application open it shouldn't be an issue. Maybe with a really old computer, but anything modern really should handle an electron app just fine
I'd prefer that. One firefox instance can easily run 10 big fat websites while using like 6GB of RAM. 10 electron apps on the other hand? 32GB RAM won't be enough.
I know that Electron is a browser. But the issue is that it's a different browser, and AFAIK Electron applications don't share libraries etc. like Chrome/Firefox tabs would, which makes Electron apps even more inefficient than web apps.
Well, there's also Tauri which requires slightly more testing since you actually use the device's built-in browser, so there might be differences. The upside is a much smaller bundle size, quick start-up times and often less RAM usage than with Electron.
What about laptop battery life? More CPU usage = less battery life. WHY DOES NO ONE GIVE A FUCK ABOUT BATTERY LIFE???
The single most reason I switched from Spotify to Apple Music is that I was sick of seeing the Spotify macOS app at the top of the "High Battery Usage" page on Activity Monitor. I also actually noticed less battery life. Fuck Electron. I avoid apps made in it like the plague.
lmao, yea. Besides, it’s not like electron is that bad either. We aren’t in 1990, why would you care if electron uses a gb of ram or ten processes or this or that… they think that native means good, but more often than not native means a shitty ugly unusable application that will work (not really) just on windows
Have you ever had, in good conscience, a problem caused by an electron app using too much resources?
Because we are, again, in 2023: the standard is 16GB of RAM, with CPUs much more powerful and with a lot of more cores and thread per cores than the past. Complaining about a PC resources being used when these doesn’t actually create a problem is like complaining about GUI being bloat; or JS/CSS being bloat.
This of course doesn’t mean electron is perfect, cause it clearly isn’t, but it’s a good enough solution that can be iterated upon (see Tauri) and improved (the DX on electron is shit). Nor that every app should be in electron.
I run slack every day. It's a bit slow sometimes but it doesn't cause any real issues. Still better than teams. I'd rather have it as an electron app than as a web app.
VS Code is electron but it's not meant to be a lightweight text editor like notepad. Must people are using it as an IDE at this point. Can you explain what's "bloated" about it?
These apps probably wouldn't exist at all if it wasn't for electron so I'm grateful for it. The purists can pound sand like always.
on the vscode comment, that’s just plain wrong. here’s vscode opening up on a base model m1 air (it’s a test project but my works codebase also opens just as fast)
on a 8gb ram m1 air, with 3/4 chrome windows, slack, postman and two node processes running. as for slack, i agree its not as snappy as say, native macos apps but it doesn’t really bother me a lot.
not everyone can afford 16 GB of RAM though, if you want to make your software accessible write it to work on as many systems as possible with few or no slowdowns or hiccups. Electron is a shitty bandaid because you're a lazy ass that doesn't want to write more efficient software for desktop and instead you keep making web applications running natively, which is and will always be wrong
It didn't cause problems since i have a lot of RAM but i still hold the opinion that just because we have a lot of RAM, we don't need to waste it. We could keep being efficient about it and get even more out of the same amount of RAM, you know. That said, if Tauri lowers the RAM usage of the same applications i'm looking forward to it.
that would change nothing to you. Unless they are seriously consuming a lot of memory and filling up processes while not needed, then it’s fine. Otherwise it means the app was developed by a bunch of monkey, but that could happen - maybe even more likely - with native software as well.
Tldr: to the end user it changes literally nothing nowadays, to the companies and the devs it changes quite a lot. And to some degree, end-users won’t have to deal with shitty ugly apps (unless the designers are jerks, in which case you are probably working in the same company as me)
From the comments that have mentioned the efficient programming languages, my guess is there's a bunch of devs in here that never got past the "c++ is hard!" stage.
The first time I saw an office app launch in my browser, I was both impressed that they got excel to work in a browser and appalled that they wanted excel to work in a browser at the same time. And I'll admit that it does perform well considering it's running in a fucking browser, but I'll still launch the native app any time I actually want to work with a file that's opened in the browser.
Keep at it, eventually things will click and you might find yourself appreciating the compiler errors and type strictness. Perhaps you'll even spend time getting rid of warnings even though it will let you run without doing that, because they indicate edge cases that might break your program in difficult to debug ways.
It's all kinda the same btw. Like you'll have different sytax and styles, but most languages have variables, loops, conditionals, functions, objects, inheritance, APIs to access OS functions like files and network, etc.
You know that "no app" and "not using the app" is the exact same user experience right? So you can just not use the app and stop complaining about it existing.
The same reason why webapps are a bad idea. We've built monstrous browser engines to do fancy stuff to pages in a bonkers language in a sandbox, and the resulting abomination is neither pages nor apps. And now we're like: we have so much expertise in shuffling page parts around to look like they're apps, let's build "real" apps out of them. It's like rejecting headphones and towing a car with broken windows around with you just in case you'll wanna listen to music: it technically works, but makes negative sense.