Snow Leopard is imminent

koffiejunkie

Executive Member
Joined
Aug 23, 2004
Messages
9,588
I disagree, having more app lib's to go through to execute a command makes an app slower. Take a assembler app and compare to a c++/VB/.net app, the assembler is going to execute much faster than the c++/VB/.net.

Comparing assembler to VB/c++/.net is a stretch.

A universal binary is simply two binaries, one PPC, one x86, smacked together in one file, called "fat binary." Only one of the two parts will execute, because, well, only one can. The same goes for libraries. Several libraries rolled into a single file. This is somewhat different from the approach taken in Linux, where there's a lib64 directory, but it comes down to the same thing. In the OSX approach, there might be a slight disc I/O penalty when initially reading the executable and libraries because it will have to read the header and then find the correct section of the file, but that only happens once, since OSX is good about keeping libraries in memory. But it has nothing to do with the speed that the code can execute at.
 
Top