News for hackers. Stuff that matters.
Re:Electron and the Decline of Native Apps by purephase on Friday December 07, 2018 @04:56PM (#18632058)
This is the crux of the anti-Electron folks that I've never understood tbh.

All things being equal, I'm sure companies would love to develop their apps using native tooling and have them simple, beautiful, accessible etc. Doing this 3 times for 3 times the cost, as opposed to once some sacrifices is the obvious reason for this widespread adoption.

Re:Electron and the Decline of Native Apps by chipotle_coyote on Friday December 07, 2018 @05:27PM (#18632265)
Well, the anti-Electron argument is that you're not necessarily doing it "three times for three times the cost." If you designed your app with the intention of being cross-platform to start with, you're writing it to have some kind of platform abstraction layer. The bulk of most applications isn't going to change.

That's undoubtedly still more expensive than doing everything Electron, sure. But it's going to produce a nicer application: lower resources, faster performance, working better with platform-specific features (e.g., macOS's Services menu). Maybe that's not worth it for all applications, but if Electron-style frameworks that lock their applications to the lowest common denominators become the norm, the overall quality of software drops.

Re:Electron and the Decline of Native Apps by purephase on Monday December 10, 2018 @02:32PM (#18650523)
When I say three times the cost, I primarily mean for the web, mobile and desktop. Not for the varying OS distributions.

Electron provides a means to handle all of those environments with some admitted drawbacks on desktop. I'm not a proponent of Electron, just stating (IMO) the likely reason for it's adoption.

Re:Electron and the Decline of Native Apps by pjmlp on Friday December 07, 2018 @05:38PM (#18632350)
I can do that only once with Qt, and have perfectly simple, beautiful, accessible apps.
Re:Electron and the Decline of Native Apps by CyberDildonics on Friday December 07, 2018 @10:30PM (#18633734)
I have no idea how this whole idea of doing something 3 times gained any momentum.

Do people not realize that you can use cross platform C++ libraries and essentially get the same program to compile on three different platforms, then just write it once? It really isn't that difficult. Use Qt, or Juce, or FLTK, the standard library and a couple of cross platform libraries for things like networking and you are in the clear.

The idea that anyone is actually maintaining three separate versions of a program is completely detached from reality.

Re:Electron and the Decline of Native Apps by solarkraft on Friday December 07, 2018 @05:37PM (#18632337)
I'm fully in support of cross platform frameworks, I just hate the Electron approach of taking the worst parts of a browser and putting it all into a gigantic, ran gobbling monstrosity.

There are good "non-native" frameworks - Qt comes to my mind first, but Flutter and the now seemingly revived WPF are also good contenders. Those are pretty great.

You can also do Electron well (VsCode), but almost no devs do it, which makes me question whether doing it well might require just as much effort as using something else.

Re:Electron and the Decline of Native Apps by justinmchase on Friday December 07, 2018 @05:47PM (#18632414)
Whats an example of a non-good electron app?
Re:Electron and the Decline of Native Apps by CyberDildonics on Friday December 07, 2018 @10:31PM (#18633739)
Atom, the ethereum wallet (worst software I've ever used) and many many more
Re:Electron and the Decline of Native Apps by seanwilson on Friday December 07, 2018 @05:49PM (#18632423)
> Doing this 3 times for 3 times the cost, as opposed to once some sacrifices is the obvious reason for this widespread adoption.

Are there any stats that back this up? It wouldn't surprise me if it was more than 3 times the cost given you'll likely have a larger team to coordinate.