The short answer (from http://developer.apple.com/documentation/Cocoa/Con ceptual/ObjectiveC/Articles/chapter_4_section_3.ht ml)
"A crucial difference between function calls and messages is that a function and its arguments are joined together in the compiled code, but a message and a receiving object aren't united until the program is running and the message is sent. Therefore, the exact method that's invoked to respond to a message can only be determined at runtime, not when the code is compiled."
It's this difference between functions and messaging that allows for all of the obj-c runtime dynamism. Categories (methods added to existing classes that you don't have the source to) and DO (essentially forwarding said messages to a separate entity - where entity can be anything from thread, to process, to computer) are two of the more interesting examples.
You forget that we're not talking about the average user, but rather the average APPLE user.
Everyone knows that we're taller, more attractive, more aromatically enticing, (prone to verbose grammer), and more intelligent than the average computer user.
As with all applications written using Interface Builder and.nib files, you can change this as you see fit. If you installed the Apple Developer Tools (available freely on their website), you can open Browser.nib under your localized folder in the Safari App (/Applications/Safari.app/Contents/Resources/Engli sh.lproj/Browser.nib, most likely). From there, simply uncheck the Textured Window attribute on the main window.
Tabless Browsing is a definite hindrance, though...
Slashdot Mirror
The short answer (from http://developer.apple.com/documentation/Cocoa/Con ceptual/ObjectiveC/Articles/chapter_4_section_3.ht ml)
n ceptual/ObjectiveC/Introduction/chapter_1_section_ 1.html
"A crucial difference between function calls and messages is that a function and its arguments are joined together in the compiled code, but a message and a receiving object aren't united until the program is running and the message is sent. Therefore, the exact method that's invoked to respond to a message can only be determined at runtime, not when the code is compiled."
It's this difference between functions and messaging that allows for all of the obj-c runtime dynamism. Categories (methods added to existing classes that you don't have the source to) and DO (essentially forwarding said messages to a separate entity - where entity can be anything from thread, to process, to computer) are two of the more interesting examples.
For more info, I suggest taking a look at http://developer.apple.com/documentation/Cocoa/Co
Ow.
Ow. Ow. Ow.
-My Eyes
You forget that we're not talking about the average user, but rather the average APPLE user.
Everyone knows that we're taller, more attractive, more aromatically enticing, (prone to verbose grammer), and more intelligent than the average computer user.
sexy
.sig links.
adj. sexier, sexiest
Arousing or tending to arouse sexual desire or interest.
Thank you for reminding me to never, EVER, click through
As with all applications written using Interface Builder and .nib files, you can change this as you see fit. If you installed the Apple Developer Tools (available freely on their website), you can open Browser.nib under your localized folder in the Safari App (/Applications/Safari.app/Contents/Resources/Engli sh.lproj/Browser.nib, most likely). From there, simply uncheck the Textured Window attribute on the main window.
Tabless Browsing is a definite hindrance, though...