Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hm.. if there's any difference in the titlebar/buttons, I can't see it.
Disappointment.
Unless it's not going to be released until last minute like Leopard.

The edges are softer on the traffic lights. I really hope they polish them this time, Leopard's look fairly rushed and not polished.
 
I thought the point of Open CL was just that, for the OS to use GPU capacity transparently in a way that has not been done before, without relying on the app developers to remember to call on that power. Can you elaborate?

There are a lot of misunderstandings about what SL, OpenCL and Grand Central will do. They won't magically turn your GPU into a CPU or automatically vectorize and multi-thread normal Objective-C code.

They are more like APIs, frameworks that programers can use to more easily multi-thread their code or run it on the GPU. Think Core Video or Core Animation in Leopard.

I'm sure Apple has spent some time re-writing parts of the OS and user apps to take advantage of them, but it won't do much for 3rd party apps till they are re-written.

Even then, there's only so much OpenCL can do, GPUs still won't be used for general purpose code, they just aren't good at it. Mostly it will help with graphic filters, video transformations, heavy duty number crunching, the types of things altivec did on powerpc only much faster.
 
Quote: It is not the same thing as having another hardware thread in your CPU complex.

I thought the point of Open CL was just that, for the OS to use GPU capacity transparently in a way that has not been done before, without relying on the app developers to remember to call on that power. Can you elaborate?

The spec for OpenCL has been public for a while now. It's not even remotely close to transparent (nor could it be, GPUs are just too different). It'll require significant effort from app developers, and only apply in specific situations, but it will be very nice for those situations.
 
can anyone comment on whether snow leopard will support the 32-bit core duo macs? I dont care about 10.7 and up, etc... I just want 10.6, and if thats it, I'm happy.

will it be supported in the public 10.6 release?
 
I'd love SL to be a FREE SOFTWARE UPDATE that will just randomly "appear" in my software update one day. :D
 
can anyone comment on whether snow leopard will support the 32-bit core duo macs? I dont care about 10.7 and up, etc... I just want 10.6, and if thats it, I'm happy.

will it be supported in the public 10.6 release?

Apple hasn't said anything officially (just as they haven't said anything officially about not supporting PPC), but my guess is yes - Core Duo systems will be supported for one more major release. Apple is usually gradualist about abandoning legacy systems, so dropping PPC should be as far as they go this time.
 
can anyone comment on whether snow leopard will support the 32-bit core duo macs? I dont care about 10.7 and up, etc... I just want 10.6, and if thats it, I'm happy.

will it be supported in the public 10.6 release?
That is a good question, because I believe only the core 2 duo's and later support 64 bit. My guess would be that all Intel would be supported. A developer reading this should know.
 
Sorry, as you can see from this photo, wot I took, it's REAL!!!

So much for Photoshop experts...:D
 

Attachments

  • elevator.jpg
    elevator.jpg
    90.5 KB · Views: 160
Cocoa and Carbon are 2 different programing languages for Mac software.

To the end user you wouldn't know the difference. Arguments over which was "better" focused on the way programmers work.
Actually, end users get a lot of functionality out of Cocoa app's that Carbon ones don't get. For instance, if you're reading this in Safari and highlight some text, the Services menu (under the "Safari" pull-down menu) has dozens of things that can be done with the selected text. The same options are largely unavailable in Firefox since it's "Carbon".

Cocoa applications get a lot of "free" functionality that Cocoa developers have to implicitly work to include. This stuff dates back to the OpenStep days and is extreemly cool.
 
So, I don't know what Quicktime X actually looks like, but reading over the descriptions in this thread, I did a quick Photoshop of what I think it might look like. I just hope Apple's lawyers don't come after me :p
 

Attachments

  • snowleopard_screenshot.png
    snowleopard_screenshot.png
    926.6 KB · Views: 1,568
So, I don't know what Quicktime X actually looks like, but reading over the descriptions in this thread, I did a quick Photoshop of what I think it might look like. I just hope Apple's lawyers don't come after me :p

I think thats awesome!
 
Actually, end users get a lot of functionality out of Cocoa app's that Carbon ones don't get. For instance, if you're reading this in Safari and highlight some text, the Services menu (under the "Safari" pull-down menu) has dozens of things that can be done with the selected text. The same options are largely unavailable in Firefox since it's "Carbon".

Cocoa applications get a lot of "free" functionality that Cocoa developers have to implicitly work to include. This stuff dates back to the OpenStep days and is extreemly cool.
Just as a clarification (before someone flames me), Carbon app's can be service aware, but it requires work that Cocoa apps just get for free. ( see http://developer.apple.com/document...al/appservices/intro/chapter_1_section_1.html )
 
What about Mail?

It would be nice to have a total remake of Mail. It could use some newer features (e.g. integration with iCal).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.