Okay, how does this dude explain native Linux apps?
Probably “Native Linux apps are made in Linux-only bullshit by useless neckbeards, and probably only run in the terminal. Real actual apps like Discord made by a for-profit corporation have to be made cross-platform.”
Aren’t Qt and GTK cross platform? I have Dolphin and Kate running on my Windows work laptop.
Yeah, he doesn’t know what he’s talking about. There is a shitload of frontend developers that specialize in web standards and technologies. Electron was developed to take advantage of that deep pool of frontend developers. The side affect, is that other OSes can just support electron and they get the developers and the applications for free. Which has been a major boon for Linux users and those looking to escape Microsoft’s vendor lockin strategy. Today might be different, but in the past, nobody was intending to support Linux by creating electron apps. If they cared so much or it was so important, they would have been using Qt and GTK prior to Electron.
What kind of shit for brains asshole is still defending Windows in 2025?
And what kind of slavering mouth-breathing teoglodyte doesn’t understand that Hannah Montana Linux negates all of these issues, will suck your dixk without hesitation, and lets you read news from four days from now.
Thank God this guy got disliked to hell.
5 downvotes are absolutely nothing compared to that level of idiocy.
I’m pretty sure you guys just took the bait. This is either satire or ragebait.
I don’t man, Hanlon’s razor feels appropriate here.
The whole reasoning and especially MacOS exclusion are so contrived that it just has to be.
Electron is the only cross platform gui toolkit…
If you ignore QT, GTK and everything else.
I’m so glad that Microsoft makes an awesome cross platfor— wait, no, but they contribute code to— hmmm … Hey, what does Microsoft do to make apps more portable again?
one of the funniest (and sadly accurate) things i’ve heard said about linux backwards-compatibility is that its most stable API is Win32. you can run really old windows software on wine because they support stuff even windows doesn’t anymore.
of course this is because the expectation is that you can just recompile old software to work on new systems, which is not really a thing on window.s
The real reasons often are:
- They want be able to hire much cheaper webdevs instead of software devs.
- Electron has a lot of built-in data collecting metrics, which they urgently need for creating a real-life KITT.
- Easy live embedding of content. Sure you can add your own solution, in fact I created ETML as a solution for this problem for my engine, all without any support for nasty scripting languages or convoluted stylesheets (style-inheritance in CSS turned me off from webdev even more than JS did). At best, it can be used for things like embedding videos on Discord, because no one else thought some universal approach, let alone one that disallows proprietary players. At worst, it’s being used for ads.
Also a lot of Windows-only apps are Electron apps, only because the manufacturer wants to go “fuck you”, even putting protections into the code just in case you wanted to run it on Linux.
EDIT: Forgot the “live embeds” reason.
Another reason is when developing the Web version first. Draw.io is a good example, where we get a bonus desktop(electron) version “for free” though the product was developed as a web app.
This is not even mental gymnastics at that point.
Mental… contortionist?
-
The user land API/ABI is stable to a fault in Linux. The kernel API/ABI is unstable.
-
Companies are cheap. They hired web devs then tasked them with building a desktop application rather then hiring people to write native apps. They had a hammer and used it to fix every problem they had.
-
macOS is just as affected by electron apps as a Linux is.
-
Electron is horrible, but it does bring apps to many an OS once Chromium is ported.
-
Open protocols or open APIs from the company would fix the non-native app problem.
The user land API/ABI is stable to a fault in Linux. The kernel API/ABI is unstable
It’s the other way around. The kernel API stable to a fault, the kernel ABI isn’t. If your application only relies on the kernel API you won’t have many compatibility issues. If you rely on userland stuff such as C++ stdlib, GTK, QT, Python, … Good luck.
-
