[MichealCodes]

The basics are not rock solid. Even a core feature such as remote management crashes and freezes every 5 minutes when you connect from a non-apple machine, many have reported this over years but Apple just does Apple. Safari is still atrocious when it comes to web api supports. The worst part is, with Apple, we do not know if these are intentional anti-competitive barriers or actual software bugs. I purchased a mac mini simply to compile apps via xcode and can say the core experience is MUCH more buggy than a fresh Windows or Ubuntu install.

Edit: Hard to call intentionally preventing support for web apis a power user thing. This creates more friction for basic users trying to use any web app.

Edit2: lol Apple PR must be all over this, went from +5 to -1 in a single refresh. Flagged for even criticizing what they intentionally break.

[selectodude]

Safari adds hours of battery life due to its hyper focus on power consumption. The level to which web API standards are affected is rather immaterial to me. I imagine we’re different consumers though.

[MichealCodes]

Adds hours of battery life to the expense of making your microphone input completely inaudible due to throttling if you background the tab it's running on.

On iOS you cannot even keep a web app running in the background. The second they mutlitask, even with an audio/microphone active, Apple kills it. Are they truly adding battery life or are they cheating by creating restrictions that prevent apps from working?

Being able to conduct a voice call through the browser seems like a pretty basic use case to me.

[socalgal2]

If you’re comparing to Chrome, tests show it’s no longer true

[ahmeneeroe-v2]

I am in the same boat. I prefer battery life

[MichealCodes]

Breaking things is not extending battery life. Battery life assumes functionality. Breaking functionality to extend it is a scapegoat and the break-whatever-you-want could be provided as a mode instead of one-size fits all, we don't care what breaks approach.

[butlike]

They said the basics are rock solid (to which I agree). What you're describing, I'd consider a "power user."

[astrange]

Why would you want to support web APIs? They're all just Google proposing 5000 new ways for advertisers to fingerprint you but doing it through "standards".

[MichealCodes]

Nice strawman. The core of webapis is about opening up lower level functionality from the sandbox/accessibility of the web. Beyond audio and video IO, there's great stuff coming with webgpu and webNN. Web apps are much safer and much more convenient than downloading an app, well in theory they could be if support wasn't regularly sabotaged to protect a corporate interest in walled gardens.

[foldr]

Are those basics? You don’t have to use Safari, and I’ve never used remote management over the 20 years or so that I’ve been a Mac user.

[MichealCodes]

If we dismiss remote management as a non-core feature shouldn't we consider installing a new browser to be advanced usage as well?

I understand that this post is about MacOS, but yes, we are forced to support Safari for iOS. Many of these corporate decisions to prevent web apps from functioning properly spill over from MacOS Safari to iOS Safari.