4 ms·

Apple releases betas of their OS specifically so that developers can try their apps on them. macOS is so prominent that Electron-using developers should have de

Apple releases betas of their OS specifically so that developers can try their apps on them. macOS is so prominent that Electron-using developers should have detected the problem and found a solution well before the general release.

ryukoposting 1y ago
I don't do desktop applications professionally (firmware is my thing) but I would balk at the suggestion that I should run a beta OS on the machine that pays my rent. What portion of, say, Slack devs actually run a MacOS beta at work? Are they regular devs, or are they in QA/test? It seems to me like the latter is the far more appropriate team for this.
- fingerlocks 1y ago
  I write macOS software (among other things). I always run the earlier betas on another machine for testing. The primary dev box gets the beta a few weeks before release. It’s never been a problem. This is 100% on electron, they didn’t do their due diligence that every Mac & iOS dev goes through every summer before the next release. It’s been two decades of the same song and dance every year. There’s just no excuse.
rock_artist 1y ago
Well, I personally know of cases Apple did explicit patching for specific apps to keep them working / avoid breaking. My simple guess is that slipped QA or wasn’t escalated from Apple’s feedback. Considering the amount of electron apps, expecting all developers and all users to update all their app (and guessing which one is Electron based) isn’t good user-experience. Let’s say the change is needed in the OS, you’d expect transition time. Also, a good UX on OS would be to notify user this app is using some API in a way that could reduce experience. but guessing and expecting only the developer and user parties without the OS side is making less sense imho.
bambax 1y ago
If the result of this policy is that users think Apple products are crap, then it's probably counter-productive for Apple, no?

ryukoposting 1y ago

I don't do desktop applications professionally (firmware is my thing) but I would balk at the suggestion that I should run a beta OS on the machine that pays my rent. What portion of, say, Slack devs actually run a MacOS beta at work? Are they regular devs, or are they in QA/test? It seems to me like the latter is the far more appropriate team for this.

fingerlocks 1y ago
I write macOS software (among other things). I always run the earlier betas on another machine for testing. The primary dev box gets the beta a few weeks before release. It’s never been a problem. This is 100% on electron, they didn’t do their due diligence that every Mac & iOS dev goes through every summer before the next release. It’s been two decades of the same song and dance every year. There’s just no excuse.

rock_artist 1y ago

Well, I personally know of cases Apple did explicit patching for specific apps to keep them working / avoid breaking. My simple guess is that slipped QA or wasn’t escalated from Apple’s feedback. Considering the amount of electron apps, expecting all developers and all users to update all their app (and guessing which one is Electron based) isn’t good user-experience. Let’s say the change is needed in the OS, you’d expect transition time. Also, a good UX on OS would be to notify user this app is using some API in a way that could reduce experience. but guessing and expecting only the developer and user parties without the OS side is making less sense imho.

bambax 1y ago

If the result of this policy is that users think Apple products are crap, then it's probably counter-productive for Apple, no?