FROM : Mark Munz
DATE : Thu Sep 06 16:32:22 2007
Come on. 64b support is different than flashy animations and you know it.
Apple has a habit of making every developer repeat the same basic work
that should be part of the system. Even with ICU included, you still
have to jump through a number of hoops to use it with NSStrings. They
know it (based on a conversation I had in 2006 at WWDC).
Rather than fix the problem once, they basically force each developer
to "fix" the problem. And this is a pattern that is decades old.
On 9/6/07, Shawn Erickson <<email_removed>> wrote:
>
> On Sep 6, 2007, at 7:05 AM, Mark Munz wrote:
>
> > and Apple
> > apparently doesn't feel addressing this issue is more important than
> > animating the views as they slide around the screen.
>
> Yeah also why did they waste time adding 64b support when the could
> have been adding something a developer could have picked up
> themselves if they really needed it.
>
> -Shawn
>
--
Mark Munz
unmarked software
http://www.unmarked.com/
DATE : Thu Sep 06 16:32:22 2007
Come on. 64b support is different than flashy animations and you know it.
Apple has a habit of making every developer repeat the same basic work
that should be part of the system. Even with ICU included, you still
have to jump through a number of hoops to use it with NSStrings. They
know it (based on a conversation I had in 2006 at WWDC).
Rather than fix the problem once, they basically force each developer
to "fix" the problem. And this is a pattern that is decades old.
On 9/6/07, Shawn Erickson <<email_removed>> wrote:
>
> On Sep 6, 2007, at 7:05 AM, Mark Munz wrote:
>
> > and Apple
> > apparently doesn't feel addressing this issue is more important than
> > animating the views as they slide around the screen.
>
> Yeah also why did they waste time adding 64b support when the could
> have been adding something a developer could have picked up
> themselves if they really needed it.
>
> -Shawn
>
--
Mark Munz
unmarked software
http://www.unmarked.com/






Cocoa mail archive

