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
In my experience, WebKit team has been extremely responsive.
The Safari bug that never was (2022)
11–20 of 94 posts
Re: The Safari bug that never was (2022)
#12[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 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?
Re: The Safari bug that never was (2022)
#13I love these kind of bug-hunting stories. The Apple engineer that fixed the bug (and remains nameless), provided an explanation, which happily surprised me. I usually read wry remarks on Twitter about the black hole that's called Radar.
> 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)
Re: The Safari bug that never was (2022)
#14[flagged]
Safari has its problems, to be sure, but it is a long, long, long way from being equivalent to old IE.
On one project I remember, around 30% of the code was there simply to make it work with IE. I've never seen anything close to that with Safari (much less 90%).
Re: The Safari bug that never was (2022)
#15I love these kind of bug-hunting stories. The Apple engineer that fixed the bug (and remains nameless), provided an explanation, which happily surprised me. I usually read wry remarks on Twitter about the black hole that's called Radar.
> 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:
Re: The Safari bug that never was (2022)
#16Earlier quoted context omitted.
My impression is that the Safari team is just very small. They are often more quirky than other browsers, and they lag in features (but not nearly so badly as IE used to). On the other hand they've brought some very welcome improvements: the :has selector and container queries being the standout ones in recent times. And their engine is more power efficient and often faster than anyone elses. EDIT: I would add: 90% s…
Really enjoying the power efficiency of Safari on a Mac, it keeps me away from the other browsers.
You can turn on lockdown mode on MacOS Ventura and it basically disables active compiler JavaScript for all sites - you can turn it back on site-by-site but it’s interesting to see what keeps working.
Benchmark scores go to ass but much of JavaScript I’m actually used is just fine.
Re: The Safari bug that never was (2022)
#17I like how they were too modest to post the developer's comment in the bug:
> "Also, this is a fantastic bug report. I don't know if I've ever seen a bug report this detailed before."
Little things like that restore faith in humanity.
Re: The Safari bug that never was (2022)
#18Earlier 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)
#19[deleted]
Re: The Safari bug that never was (2022)
#20[flagged]
Safari has its problems, to be sure, but it is a long, long, long way from being equivalent to old IE. On one project I remember, around 30% of the code was there simply to make it work with IE. I've never seen anything close to that with Safari (much less 90%).
I remember having to support IE versions 6-11 with a couple of sites I worked on and wondering why Microsoft wouldn't just port the technically superior Tasman engine used for IE for Mac to Windows… it was so much better than Trident at handling CSS and could do things that Trident couldn't until a decade later like properly render transparent PNGs without hacks.
And yeah, Safari has posed far less of an issue for me than IE did.