News for hackers. Stuff that matters.

A comment on Swift 5: start your engines. Parent comment

Re:Swift 5: start your engines by protomyth on Wednesday August 09, 2017 @04:22PM (#14973210)
Yeah, right, that is some serious BS right there. I've filed radars on the Finder (multiple with reproducible crashes), location data, and Quicktime and it holding onto external drives. The only one they have ever fixed is the Quicktime bug but it reappeared later then went away again.

Apple is horrible about bugs and providing feedback. Why the heck would I need to file a radar anyway? Doesn't someone at Apple check the examples to make sure they still work? These are the examples Apple uses to promote and teach the language and how to build apps.

[ Parent | on HN ]
Re:Swift 5: start your engines by saagarjha on Wednesday August 09, 2017 @04:30PM (#14973286)
> Apple is horrible about bugs and providing feedback.

Yes, they can be a bit tight-lipped. I have found that they're pretty quick on fixing documentation though. They won't tell you that it's resolved, but it's usually updated within a couple of days.

> Doesn't someone at Apple check the examples to make sure they still work?

I'd expect that they do, but some slip through the cracks. Maybe on of the Apple engineers in this thread could weigh in?

[ Parent | on HN ]
Re:Swift 5: start your engines by chc on Wednesday August 09, 2017 @09:51PM (#14975622)
Apple are super slipshod about their documentation in general. Hardly a day goes by that I don't get a Stack Overflow comment telling me that some link to Apple's docs is broken.
[ Parent | on HN ]