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.
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.
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.