Live data from Hacker News

The Safari bug that never was (2022)

obyford.com

21–30 of 94 posts

Re: The Safari bug that never was (2022)

#21
post #7

Earlier quoted context omitted.

Really enjoying the power efficiency of Safari on a Mac, it keeps me away from the other browsers.

It’s disheartening that Google and Mozilla seem so disinterested in trying to match or exceed that power efficiency. I like having multiple options for web browsers but because of the difference is so stark it’s only actually a choice on desktops.

[deleted]

Re: The Safari bug that never was (2022)

#22
post #5

Earlier quoted context omitted.

> It's clear they hate the web I feel that they're just organizationally incompetent. They're moving too fast and lack adequate quality assurance. macOS itself is getting much buggier overall. Craig Federighi should be fired.

I like Federighi's public persona quite a lot, but yes, I have too been concerned about macOS's quality since he took over. Any books / inside reports I can read about his tenure that would provide more context on him & his management of macOS?

Some engineers post about their past experiences sometimes.

https://tidbits.com/2019/10/21/six-reasons-why-ios-13-and-ca...

https://twitter.com/taquitos/status/1599824249107406848

Re: The Safari bug that never was (2022)

#23
post #7

Earlier quoted context omitted.

Really enjoying the power efficiency of Safari on a Mac, it keeps me away from the other browsers.

It’s disheartening that Google and Mozilla seem so disinterested in trying to match or exceed that power efficiency. I like having multiple options for web browsers but because of the difference is so stark it’s only actually a choice on desktops.

Mozilla has invested a lot of effort into power efficiency. It's a pretty painful treadmill considering how often platform-level things change (OS X compositor changes, OpenGL being killed, etc) which means you end up losing ground and having to rearchitect or rebuild stuff to get back to where you were previously.

Part of Firefox's power efficiency challenges on OS X are specifically due to how Apple designed the platform, and not something wrong with the browser. They've had to incrementally add in lots of machinery to feed the OS the information it suddenly wants.

If Safari has better power efficiency on OS X (I don't doubt it), that's partly just because they work next door to the video driver and OS compositor people. It's not because Mozilla doesn't care. (Does Google care? I can't say for sure, but I suspect they do.)

Re: The Safari bug that never was (2022)

#25

Earlier quoted context omitted.

It’s disheartening that Google and Mozilla seem so disinterested in trying to match or exceed that power efficiency. I like having multiple options for web browsers but because of the difference is so stark it’s only actually a choice on desktops.

Mozilla has invested a lot of effort into power efficiency. It's a pretty painful treadmill considering how often platform-level things change (OS X compositor changes, OpenGL being killed, etc) which means you end up losing ground and having to rearchitect or rebuild stuff to get back to where you were previously. Part of Firefox's power efficiency challenges on OS X are specifically due to how Apple designed the pl…

Part of the difference is compositor integration for sure, but there's also design decisions that factor in, like how Safari has throttled JS in non-active tabs for years, where Chrome only started doing this last year. One gets the impression that Google at least is more concerned with Chrome being an attractive app platform than they are with it being responsible with user resources.

Re: The Safari bug that never was (2022)

#27
Safari seems to have been getting more developer attention this last year. This is good but also has resulted in a number of bugs and regressions as they move fast. Same is happening on Chromium.

I likewise have been involved in a similar bizarre bug. We wrote up a very detailed report with a reduced test case but sadly it has not received much attention. https://bugs.webkit.org/show_bug.cgi?id=247020

Re: The Safari bug that never was (2022)

#28
post #2

Good to know they are serious about fixing things. Hopefully my bug, which crashes Safari (!) with CSS only, will be fixed soon: https://bugs.webkit.org/show_bug.cgi?id=249575

My previous experience says that it will take several years to fix it.

Just like in IE, you need to make silly workarounds.

Re: The Safari bug that never was (2022)

#29
post #15
post #13

Earlier quoted context omitted.

> and remains nameless WebKit is open-source, so it is actually one of the few Apple projects where the developers do not not remain nameless (the other big one being Swift). > the black hole that's called Radar IIRC WebKit has its own bug tracker, hence why you get better response times. Radar itself is still a terrible and demoralizing experience (from a developer point-of-view)

> IIRC WebKit has its own bug tracker, hence why you get better response times. Radar itself is still a terrible and demoralizing experience (from a developer point-of-view) The funny thing though is that Apple still sends WebKit bugs into Radar to work on them: https://bugs.webkit.org/show_bug.cgi?id=232939#c6

That isn’t surprising. Even if the work is being done publicly, it still needs to be tracked and project-managed internally by the team.

Re: The Safari bug that never was (2022)

#30
post #5
post #3

[flagged]

> It's clear they hate the web I feel that they're just organizationally incompetent. They're moving too fast and lack adequate quality assurance. macOS itself is getting much buggier overall. Craig Federighi should be fired.

I'm not usually a backwards person, but I got the Macbook 2016, and with every release it got worse. Now I'm on NixOS on a Lenovo and while there are regressions, they're usually temporary. Regressions on MacOS seemed permanent.
Post reply on HN