What do you mean by OpenCL isn't deployed yet? It's been in and supported since 10.6.0,
Umm, I've known the primary developer working on this at AMD since high school. It's not shipping yet. And NVIDIA's support isn't shipping yet either. I'm not sure what your demo apps do, but they're not using the vendor-developed OpenCL stuff. Probably just the CPU. Can't really get into any more detail in a public forum.
Here's something Apple might consider... Being able to adjust FONT SIZE system-wide. With higher resolution panels like that of the 17" MBP (1920 wide) a lot of text is just too small. Thankfully for my file manager I use Path Finder which is a lot more configurable than Finder (where you can only adjust filename font size).
Fixing some of the memory leaks and memory corruption in Safari would be nice too. Not to mention the bucket-load of bugs and poorly implemented features (address recognition) in Mail.
The quality of 10.6 in terms of stability has been much better on my Intel MBP than 10.5 ever was on my PowerBook, but generally speaking, I'm a little dismayed at the lack of attention to detail in many areas. I know, attention to detail is what Apple is known for. When compared with most any other company, they're head-and-shoulders above, but that's besides the point.
There are some bullet points about the Mac App Store approval process on TUAW.com right now. You're definitely not allowed to implement your own protection into your software. They do allow background tasks so long as you get the user's permission (this would have excluded a ton of software I've had in the planning stages otherwise).
Here are some points for rejection (from
TUAW):
According to Apple, your Mac app will be rejected if:
It is a "beta," "demo", "trial," or "test" version
It duplicates apps already in the App Store, particularly if there are many of them
The developer is "spamming" the App Store with many versions of similar apps. You will also be removed from the Developer Program if this occurs.
It is not packaged and submitted using Apple's packaging technologies included in Xcode - No third party installers are allowed.
It require license keys or implements its own copy protection
It spawns processes that continue to run after a user has quit the app without user consent
It has metadata that mentions the name of any other computer platform
It uses location-based APIs to control vehicles, aircraft, or other devices (Saying goodbye to my Macbook Air tank project. Sigh.)
It uses location-based APIs for dispatch, fleet management, or emergency services
It has misspelled Apple product names in its name (i.e., GPS for Imac, iTunz)
It looks similar to Apple Products or apps bundled on the Mac, including the Finder, iChat, iTunes, and Dashboard
Your user interface is "complex or less than very good"
It changes the native user interface elements or behaviors of Mac OS X (Well, that just wiped out 90% of the best Mac apps in a single, flaming fist punch.)
It creates a store inside itself for selling or distributing other software (i.e., an audio plug-in store in an audio app)
Your game portrays realistic images of people or animals being killed or maimed, shot, stabbed, tortured or injured. (Such as Counter Strike, Halo, and pretty much every other good video game ever produced.)
"Enemies" within the context of your game solely target a specific race, culture, a real government or corporation, or any other real entity. (I wonder if this applies to zombies...)
It contains user generated content that is frequently pornographic (like "Chat Roulette" apps)
Here's good article from TUAW about two points, one expressly from the list and the other from the way the iOS store works. Demos/trials and upgrade pricing:
http://www.tuaw.com/2010/10/20/app-store-for-mac-highlights-two-major-app-store-flaws/
Previous Topic
Index
