Okay, even though I swore that I wouldn't add fuel to this fire,
I'm totally confused as to the level of confusion that I'm reading
(discounting the C/C++ vs. ObjC arguments). From what I see,
Carbon isn't going away, it's just not getting the full 64 bit
monty. How does that affect my Carbon UI development? It doesn't
unless I need to display a 2TB+ image in a window, or display 2TB+
of cell contents simultaneously in a table (yeh, right). So my
confusion is that I don't understand how not having a 64 bit UI API
will really affect Carbon users.
For the moment it won't if you don't have any use for 64-bit support,
but read my response to your other post. I think the issues we'll be
facing in the future are pretty clear.
If I've got a huge data model that requires 64 bit value handling,
I don't need to use Carbon UI functions, so I'm not limited by
Carbon's lack of 64 bit underpinnings. Is not having a "UI is 64
bit" checkbox on product datasheets that big of a deal for
customers' perception of a product?
Please illuminate my darkness - what am I obviously not seeing?
The writing on the wall.
Luke Skywalker: "I'm not afraid."
Yoda: "You will be."
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
