2 ms·
...but that's the key point, isn't it? That the existing implementations don't really work. Just like there were plenty of "non-lame" MP3 players and plenty of
by nl 10y ago
...but that's the key point, isn't it? That the existing implementations don't really work. Just like there were plenty of "non-lame" MP3 players and plenty of smart phones and plenty of tablets...that all didn't really do the job.
Making something work great that already kinda exists, that people have tried and failed to really make great, isn't that exactly Apple's MO?
I think we agree entirely. Incremental innovation - fixing things that are broken.
The performance of Swift doesn't matter much to Apple. Swift is a demand-pull thing: Developers care about iOS, and will pay the horrible performance tax. The developer experience for iOS developers has always been horrible but it has one thing that matters more than that: users.
- mpweiher 10y ago>Incremental innovation - fixing things that are broken. Yes and no. Yes in that it is incremental in a way. No in that all of Apple's "revolutionary innovations" have been of this sort, not that I am saying the Touch Bar is necessarily of that scope. > The developer experience for iOS developers has always been horrible Do you think there might be a point in making it less horrible?