UnitedWorx

amazon should stop the nonsense and focus on their core services. its 2017 and its a bloody nightmare trying to figure out which sellers sell to your country through amazon. P.S. no amazon you can not complete with apple messages coz you dont have the billion devices apple has with messages enabled out of the box! oh and nobody will stop using messenger, viber, whats app coz you decided to do a messages app.

help? you mean make it even harder to get hold of an iPhone 7 Plus!

Waiting on apple to refresh their rMacbook pro line so I can upgrade my 2012model! no point on upgrading to an almost 2 year old rMacbook pro when you know a refresh is imminent! No wonder why sales numbers are down!

Partly its Intel to blame thought with a slow processor upgrades. Eagerly waiting on apple to dish intel in favor of the own processors! Recent A series processors have shown that apple is aggressively improving their processor line and its very close to the performance of desktop class processors! I am sure deep into their labs they do have A series processors that beat every single desktop processor out there running on prototype macbooks. They have done this before (move prom power pc to inter) so I am sure they know how to do it best! Take your time apple!

Germany 11,989 requests!!! What the hell is going there?

https://daringfireball.net/thetalkshow/139/federighi-gruber-transcript

John Gruber: How do you manage as the chief mofo in charge of this? How do you manage the enthusiasm that you clearly have for Swift and, what to me seems like a sincere belief that Swift is the way forward — with the necessary conservativeness that you need so that there still has to be a lot of Objective-C written? How aggressive can you be about putting teams on, “Sure, go ahead and do that in Swift”?

Craig Federighi: People here are idealistic yet really pragmatic, and I think you see that as an Apple characteristic in many, many elements of what we do. And so, teams know, what the nature of what we’re trying to get done in their area in any given year, the nature of their code base, whether Swift is the right answer for them, or where it’s the right answer. Even teams where, for one reason or the other, they can’t jump right on Objective-C — or rather Objective-C conversion to Swift now. They then use Swift heavily for writing all their unit tests, which is great because then at least as they’re introducing new APIs, they’re experiencing their own APIs in Swift and then … sort of eating their own dog food in that regard. We do have some constraints internally which we’re addressing, but because we … I mean, it’s something in our closet a little bit, but we still support running 32-bit apps on the Mac. And the 32-bit runtime doesn’t actually support Swift right now. And so, what that means is that if we implement a framework that’s available to 32-bit code, we actually can’t write it in Swift. If that code, if that framework is used across iOS and OS X — as many of our frameworks are — that introduces a little stumbling block as well. So teams recognize what’s practical and what’s not practical and find ways to use Swift wherever they can. There’s no shortage of enthusiasm.