| Threads as a service!? |
[Mar. 6th, 2008|10:26 am] |
In Apple's SDK announcement slides, they list the following stack:
Core OS, Core Services, Media, Cocoa Touch
Fine. Kinda silly and arbitrary past the kernel/user boundary, but what I found most hilarious is that "Threading" is listed in Core Services (along with "Address Book" and "SQLite"), instead of in Core OS (which has things like "Sockets" and "Power Management".
Is that why threading sucks so much on Macs and iTunes can't do more than 1 thing at a time well? Because it's all in userspace? :-) |
|
|
| Comments: |
only 10 features per slide plz!
Well, of course that's where the threading API would be, and now of course there are the concurrent operation widgets implement at that level, too :P
![[User Picture]](http://p-userpic.livejournal.com/5887295/515656) | From: ![[info]](http://p-stat.livejournal.com/img/userinfo.gif) jwz
2008-03-06 06:54 pm (UTC)
| (Link)
|
Maybe by "threads" they meant "t-shirts".
![[User Picture]](http://p-userpic.livejournal.com/52976608/869684) | From: aca
2008-03-06 08:48 pm (UTC)
| (Link)
|
I love you, man. :)
lol, there may be something to that. ;)
But, yeah, that's the threading API. Their abstraction layer isn't terrible. Unfortunately, iTunes is still carbon-based, so the threading library is a little... behind.
![[User Picture]](http://p-userpic.livejournal.com/66304696/780805) | From: jdev
2008-03-06 08:56 pm (UTC)
| (Link)
|
Not that that was entirely a serious question, but it was 1:1 onto Mach threads the last time I looked.
Edited at 2008-03-06 08:57 pm (UTC)
Yeah, the posix api is all userland side interfacing with 1:1 mach threads. (I guess It could have changed, I haven't programmed 10.4 or 10.5)
they probably mean mainly that's the framework the header files for threads are... i mean they're talking about the sdk right | |
