Earlier quoted context omitted.
Not every developer runs a Macbook. Like many others for my laptop I use Linux running on a cheap ThinkPad with a quarter of the specs of the one you mentioned. ( I could afford to buy an overpriced Macbook, but I like my rugged $100 ThinkPad. ) As I stated elsewhere in this thread, vscode absolutely chews up my battery power. That's a practical concern. If I run several Electron apps on my laptop I'd be lucky to get…
As someone who spent years complaining about the lack of cross-platform apps that I could run on Linux, I'm grateful everyday for Electron and for MS for using it for VS.Code. The fact that it works the same on OSX and Linux is even better.
Electron apps cannot be submitted to the Apple store
391–400 of 441 posts
Re: Electron apps cannot be submitted to the Apple store
#392Earlier quoted context omitted.
How short are memories. I remember how Microsoft was vilified for supposedly having secret Windows APIs that allowed Microsoft apps to get better performance. That was mostly made up and even if such APIs existed, any program could have used it. Even at the height of corporate arrogance Microsoft didn't dream of banning developers for using undocumented APIs. Apple seems intent on becoming more evil than Microsoft ev…
Apple wants to own the user's machine. They want to make it so their computers run only the software they approve. This is already true for iOS and it's only a matter of time before it also becomes true for macOS. It's the opposite of a free system. Giving up software freedom for "ease of use" seemed like a fine deal at first but then Apple started making decisions that don't quite align with what neither users not d…
Re: Electron apps cannot be submitted to the Apple store
#393Earlier quoted context omitted.
> there's a crowd in here that restates the same three points about memory, performance and native UI about once a week. Where else would users complain about undesirable developer trends if not on a developers' community?
You are right and I am sorry, that was unnecessary. For the record, I do think there are problems with Electron, just not the ones usually mentioned. A big (huge!) problem in my opinion is that two windows can't share JS context. It's the reason why VSCode is way behind in multi-monitor support for instance.
Re: Electron apps cannot be submitted to the Apple store
#394Earlier quoted context omitted.
No, I don't, but even if there are no such alternate packages, that doesn't mean it's OK to use one that you can't sufficiently understand. If you can't find an acceptable package, then I'd absolutely recommend writing that functionality yourself. connecting to an IMAP server and responding to events aren't complicated tasks, after all.
This is entirely feasible but what percentage of people can write replacements for problematic tools and what tools can they afford to replace time?
Re: Electron apps cannot be submitted to the Apple store
#395Earlier quoted context omitted.
Yes, this is the thing. The option isn't electron vs native, it's electron vs nothing.
Often, nothing is better than the Electron equivalent. Case in point, if I run Slack in Safari, it runs better than the electron version. Functionally, it’s identical, except the scrolling is now native and feels a bit better integrated in macOS. So what’s the point?
(That isn't to say that the web version of Slack isn't horribly engineered too, but it poses far less of a problem)
Re: Electron apps cannot be submitted to the Apple store
#396Earlier quoted context omitted.
I work in public digitisation and while we don’t build the apps, we’re now required to publish them if we want our name as the publisher. So I’ve had the pleasure of setting up our development account and it’s easily the works service I’ve ever had to go through, and we operate 300 different IT systems, some are old terminal systems that run on mainframe. I’m not sure why the process was so complicated either. A coup…
> we’re now required to publish them if we want our name as the publisher. That seems reasonable to me -- they're just saying that if you want to be listed as the publisher, you need to be the publisher...
The result is 98 muniplacities having to pay Apple developer fees, but it gets better because the app can’t be called the same thing anymore. So now there are 98 apps instead of one. :p
I mean, I guess our central digitisation agency should really just pick it up, but the bureaucracy doesn’t work like that.
Re: Electron apps cannot be submitted to the Apple store
#397Re: Electron apps cannot be submitted to the Apple store
#398Earlier quoted context omitted.
is it possible to write a GUI app that looks native in all common desktop environments yet?
Sure, if you write the GUI portions in the native toolkit and factor out the backend into your cross-platform language of choice.
Re: Electron apps cannot be submitted to the Apple store
#399Re: Electron apps cannot be submitted to the Apple store
#400Earlier quoted context omitted.
> we’re now required to publish them if we want our name as the publisher. That seems reasonable to me -- they're just saying that if you want to be listed as the publisher, you need to be the publisher...
Sure, but that’s not actually what happened. I didn’t go into detail with that part, because it’s fine. We’re fine with someone else being the publisher and listed as such though, but you’re not allowed to do that on behalf of others anymore. The result is 98 muniplacities having to pay Apple developer fees, but it gets better because the app can’t be called the same thing anymore. So now there are 98 apps instead of…
It's not really fair to expect Apple to resolve or work around your own organizational problems.