Yes & no is my take. Usually no Linux support means a free software app is born to replace it which is awesome–or better, a previously-obscure or deserves-revitalization free software application gets its moment in the sun (rather than reinventing shit that already works cough Matrix). …The downside is when employers/client/etc. demand you use some proprietary sludge so luckily you have Electron app to get over that hurdle–tho 90% of apps in this category largely should be fine in PWA form instead of needing Electron.
It’s not just “opening a website in a browser”. The UI itself is displayed in a WebView, but Electron (and Tauri etc.) also have code running outside the WebView which interfaces with native APIs etc. Just for a simple example - a normal browser application couldn’t open a file on your drive before without showing a dialog (and it still can’t without getting permission first), which Electron etc. can.
And this code is absolutely cross-platform. So how is it rich to call an application with a cross-platform UI and cross-platform functionality “cross-platform”?
Would you prefer new terminology? Like platform-neutral UI? The way I see it there’s CLI, GUI, and WebUI. When discussing platforms for the first two, were discussing the OS, but for the last the platform is the browser.
I honestly don’t care what the user interface is as long it’s efficient at getting done what I need it to do.
deleted by creator
Cross-platform apps - The Linux experience:
deleted by creator
No, but when I have the choice between a platform-specific software I like and a cross-platform software I don’t, I usually go with the former.
I’ve used Linux for much longer than Electron even exists, and I’ve learned to live with what I have available.
Yes & no is my take. Usually no Linux support means a free software app is born to replace it which is awesome–or better, a previously-obscure or deserves-revitalization free software application gets its moment in the sun (rather than reinventing shit that already works cough Matrix). …The downside is when employers/client/etc. demand you use some proprietary sludge so luckily you have Electron app to get over that hurdle–tho 90% of apps in this category largely should be fine in PWA form instead of needing Electron.
I am glad that atleast it ends there. It could have been worse.
Though calling them “cross platform” when all you’re doing is opening a website in a browser is IMO a bit rich. Is lemmy cross-platform, too?
If at least they had native UI elements on each platform, we’d be getting somewhere. Fitting design and all.
It’s not just “opening a website in a browser”. The UI itself is displayed in a WebView, but Electron (and Tauri etc.) also have code running outside the WebView which interfaces with native APIs etc. Just for a simple example - a normal browser application couldn’t open a file on your drive before without showing a dialog (and it still can’t without getting permission first), which Electron etc. can.
And this code is absolutely cross-platform. So how is it rich to call an application with a cross-platform UI and cross-platform functionality “cross-platform”?
Would you prefer new terminology? Like platform-neutral UI? The way I see it there’s CLI, GUI, and WebUI. When discussing platforms for the first two, were discussing the OS, but for the last the platform is the browser.
I honestly don’t care what the user interface is as long it’s efficient at getting done what I need it to do.