How Snow Leopard Cut ObjC Launch Time In Half

MBCook writes "Greg Parker has an excellent technical article on his blog about the changes to the dynamic linker (dyld) for Objective-C that Snow Leopard uses to cut launch time in half and cut about 1/2 MB of memory per application. 'In theory, a shared library could be different every time your program is run. In practice, you get the same version of the shared libraries almost every time you run, and so does every other process on the system. The system takes advantage of this by building the dyld shared cache. The shared cache contains a copy of many system libraries, with most of dyld's linking and loading work done in advance. Every process can then share that shared cache, saving memory and launch time.' He also has a post on the new thread-local garbage collection that Snow Leopard uses for Objective-C."

Comments

Re:I've heard that before....

[Anonymous Coward]

Isn't caching executables and shared libraries something Unix and variants have been doing for ages too? Way to stay ahead of the game, Slow Leopard :P

Re:Commen Sense Sharded Library

[bonch]

Okay, it's time to bring out the fucking guns.

Jesus fucking christ, you goddamn idiots. Read the fucking article. This is about selector caching for Objective-C. Your fucking piece of shit Linux doesn't do that, you yogurt-eating, functionally brain-dead simpleton. Please douse yourself in gasoline, jump off a building, and ignite yourself so that you explode onto the crowd below, raining guts and vital organs like a grotesque storm of stupidity.

FUCKING HELL. RAWR.

Re:Apple made a rod for their own back with Obj-C

[fnj]

So in other words you can't think of any substantive arguments in favor of ObjC?

Re:Apple made a rod for their own back with Obj-C

[fnj]

But instead of saying "I have seen perfection," can't you come up with any cogent explanations of exactly what features make ObjC nso divine?