Originally Posted by ghostface147
It's possible that it is, and that's what I was thinking. However if SL is going to be available in September (not knowing when in September of course, typical) then it would RTM probably sometime in mid-August at the latest based solely on my assumptions. I would hope that they still wouldn't have debugging turned on this late into development. Oh well, I still am happy with SL so far.
Originally Posted by a_greer
Is it in debug mode?
This is a common misconception with developer builds of pre-release operating systems. There is no "debug mode". Every operating system release Apple has put out is created with a fixed version of the compiler determined way before the OS ships, using release build options (that is, -Os etc.) Debugging symbols are never left in released build trains. Teh snappy that happens in later builds is almost ALWAYS the result of optimizations done by tuning algorithms--determining what's slow and changing how it works so it's faster. There is no "compile with Debug options" switch that gets turned off when they release, nor is there some switch to "GCC with the fast options enabled".
That would be terrible software engineering, as the compiler, build tools, etc. are all under development while the operating system is under development, and therefore the operating system is generally built with the last released STABLE compiler. For example Clang (LLVM) is the "latest greatest" compiler from Apple, but right now very few applications in Mac OS X are built with it. At the beginning of the development cycle, the Clang/Xcode team worked with the Mac OS X developers to determine a small set of internal applications that could be compiled with Clang to stress test Clang itself. Similarly Xcode.app was the only 64-bi application in Leopard, so that the Cocoa team could find 64-bit bugs and defecencies during the Leopard development cycle.
Finally, leaving debugging options on is not an option because generally they bloat the executable size, which can impact too many other metrics. You don't want your final product to be 20-40% bigger then it actually needs to be when you are trying to get feedback on how fast the product installs, how much room it takes up and how fast it executes. Again there are exceptions--some things that are under rapid development get debug symbols left in, usually because a developer forgets to start stripping it. But generally most groups are stringent about removing debug symbols. (Anybody developer that's gotten a lot of ???? in their backtraces, or tried to trace through a function in an open source framework like CoreFoundation, knows these frameworks are stripped long before we get them on our computers).