4 ms·
Not disagreeing, but observing Apple has a big scale problem: They sell millions, hundreds of millions of things. They are remarkably small in the clue departme
by ggm 4y ago
Not disagreeing, but observing Apple has a big scale problem: They sell millions, hundreds of millions of things. They are remarkably small in the clue department, so the clue density remains high (this is the MIT theory of clue: the more people you have the thinner the layer of clue has to spread until almost everyone is virtually clueless)
View it from their point of view: a spigot will deliver 20,000 important, believable problems to everyones desk like a mailman opening the letter-to-santa sack in December. Every desk: Which one(s) do you look at first? Note, all of them are from people of good intent, not fools. The fools are railing on bulletin boards.
BTW I have met Apple engineers who write things. Important things, like the TCP/IP stack for the iPhone. There are two of them. They can't write amazing code, and triage 20,000 bug/improvement inputs at the same time. Sometimes, they're at standards meeting handling fools like me.
Sure, there are ass-hats, but the vast bulk of the time Apple is drowning in good input, and has to triage. The example listed here probably affects 1,000 to 2,000 developers, and a critical bug probably has to affect 150,000 people to get traction.
or you can spend $99 and prioritize your problem.
I had this problem with Microsoft and X509 about 15-20 years ago, (selection of which client certificate to identify a user when there is a certificate subjectName collision) -There was precisely one expert able to fix it, I was ringfenced from them, talking to a consultant and I had the great joy of hearing how much it would cost him to even TRY to get their attention on this problem, which btw, affects the US Government, so its not like it doesn't have "scale" behind it.
This is a problem you get, if you have hundreds of millions of customers.
- manmal 4y agoDo you think this problem is intractable? I often wonder how Apple can keep posting these quarterly results of a gazillion dollars and still not reply to my Feedbacks for months or years - of things that are very clearly broken! As a dev, I‘m paying them ca 2k per year in hardware costs. Sure sounds like the incentives to really fix this would be there. Apple often claim they are among the most innovative companies. They don’t seem particularly innovative in this space. Eg. the Feedback app looks like it’s been made by a single person over the span of a week.
- ggm 4y agoI don't think the problem is intractable, but I also don't think the problem is going to be fixed very soon. It's like google. I doubt any googlers here like it when people use "complain on HN" to fix "my account was locked" stuffups. The bottom line is that with 125,000 employees for 1.5 billion users, they don't have much choice unless people pay. (I paid for google one in part to have at least SOME paid access to helpdesk and so far, they've been very nice) Apple is very focussed on profit. There often is very little profit in this space and the more time it sucks to decide #WONTFIX the more it cost you. In that model, which is not a good model, but in that model, doing less engagement pays back better if you make really really good product with low overall bug/problems. For more normal people making normal things, its suicidally bad. Ignore your customers at your peril.
- cmeacham98 4y ago> I often wonder how Apple can keep posting these quarterly results of a gazillion dollars and still not reply to my Feedbacks for months or years - of things that are very clearly broken! I mean, you said it yourself: > I‘m paying them ca 2k per year in hardware costs. Despite the fact Apple hasn't responded in years, you still pay them 2k a year. Companies exist to make a profit, and Apple has seemingly correctly identified that they can skimp on this area and people will still send them money.
- feet 4y ago[flagged]
- spoonjim 4y agoThey could permanently lose every customer who has ever sent them a Feedback and the CFO wouldn’t even notice
- lapcat 4y ago> They could permanently lose every customer who has ever sent them a Feedback and the CFO wouldn’t even notice Most of the customers who file Feedbacks are app developers, so yes, they would notice, because the App Store would suddenly be empty.
- thelittleone 4y agoI'd like to believe that's the issue but my own experience leads me to believe they really don't care about external feedback. Apple heritage is "the customer doesn't know what they need" which is at odds with customer feedback. It's almost as if they view incorporating feedback as weakness which is fair enough in the earlier years.
- unmole 4y ago> BTW I have met Apple engineers who write things. Important things, like the TCP/IP stack for the iPhone. Doesn't the iPhone, like other Apple products use the FreeBSD networking stack?
- ggm 4y agoThe short answer is only vestigially. TCP/IP has diverged into multiple competing versions across the OS world. Things like Multi-path TCP, BBR and other congestion control logic, the incorporation of things like Happy Eyeballs (v6/v4 preferencing) and some basic modelling of end-to-end RTT/jitter in the kernel is all pretty much post-FreeBSD. "write" is the active word here: Leffler and Joy "wrote" the TCP/IP stack for BSD. Lots of people are "writing" TCP/IP code. Maintaining? Modifying? Improving? Augmenting? Bugfixing? I know these guys were insanely busy.
- tobr 4y agoI got the impression from the post that the problem in this case, like in many other cases with Apple, was a lack of documentation. Why would this not be documented? It would save everyone time, sweat and tears if the documentation was OK.