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.
The Safari bug that never was (2022)
21–30 of 94 posts
Re: The Safari bug that never was (2022)
#22Earlier 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?
https://tidbits.com/2019/10/21/six-reasons-why-ios-13-and-ca...
Re: The Safari bug that never was (2022)
#23Earlier 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.
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)
#24Re: The Safari bug that never was (2022)
#25Earlier 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…
Re: The Safari bug that never was (2022)
#26[flagged]
Re: The Safari bug that never was (2022)
#27I 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)
#28Good 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
Just like in IE, you need to make silly workarounds.
Re: The Safari bug that never was (2022)
#29Earlier 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
Re: The Safari bug that never was (2022)
#30[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.