Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I still think "Snow Leopard" is a remarkably poor choice for a name. :rolleyes:

They're arguably the most stunning of all the big cats. They are also endangered species (there are only ~5,000 left in the wild), so hopefully “green” Apple donates some money to saving them from some of the profits they make selling an operating system baring their name.

I see Adobe, IBM, Microsoft and Nikon on the list of donors for the Snow Leopard Trust, but not Apple.
 
Seed notes or it didn't happen.

Mac OS X version 10.6 Snow Leopard build 10A190 Developer Seed Note

Summary

Since our first seed of Snow Leopard at WWDC '08 we've added much to Snow Leopard. Most notably you'll see changes in areas like:

- Basic reading and editing support for Microsoft Exchange in Mail, iCal and Address Book.
- Multicore enhancements including changes to queue management in Grand Central, syntax changes, and blocks in C++/GDB.
- The Finder is now partially rewritten in Cocoa.
- A simplified install experience.

In addition to testing your own applications and the updated technologies in Mac OS X, please pay particular attention to the following areas and report any issues such as incompataibilities or usage problems.

Installation Instructions

A. Install Snow Leopard using hard disk partitions:
Requirements:
Three hard disk partitions internal or external (you could use 2 but 3 recommended)

Hard disk partitions setup:
Partition 1 - download Snow Leopard disk image here
Partition 2 - restore disk image onto this partition
Partition 3 - partition to install Snow Leopard on
(Partition 3 is optional, you can install onto Partition 1 if you only have 2 partitions)

Procedure:
1. Boot off partition 1, using Disk Utility, restore the Snow Leopard DVD Disk Image onto partition 2

2. Boot off partition 2 and install Snow Leopard onto partition 3
OR if you only have 2 partitions:
2. Boot off partition 2 and install Snow Leopard onto partition 1

Note: Use System Preferences : Startup Disk to pick startup volume

OR

B. Burn bootable DVD for installation:
Requirements:
1. A DVD drive capable of burning double-layer DVDs
Here's how to check to see if you have such a drive:
- Launch "Systems Profiler"
- Under Hardware, click on "Disc Burning"
- Under "DVD-Write", if "+R DL" is listed then your machine has the ability to burn double layer DVD discs.
2. A blank DVD+R DL media

Procedure:
1. Launch Disk Utility
2. Click the Burn button in the Toolbar*
3. Navigate to and select the downloaded DVD disk image then click the Open button
4. Insert a blank DVD+R DL disc into your DVD burner
5. Click the Burn button

After burning, install Snow Leopard from the burned DVD.

Areas of Focus

Microsoft Exchange Support

Snow Leopard now contains additional support for Microsoft Exchange 2007 via Mail, iCal and Address Book. While there is support for basic browsing, creation and editing of Microsoft Exchange data, much functionality and polish is still forthcoming which may impede full Exchange use in this seed. Please focus on the areas of Microsoft Exchange outlined below:

Setting Up Exchange

Mail includes an autodiscovery feature to streamline the configuration process:
1. Open Mail preferences and click the plus button to add a new account.
2. Enter your Microsoft Exchange email address and password and click "Continue."
3. Your server settings will be auto populated and you can choose to simultaneously configure Address Book and iCal for use with Microsoft Exchange as well.
4. Verify the settings are correct and click "Create."

If the your server settings are not automatically configured, after step 2 you can select "Microsoft Exchange 2007" as a new account type and manually enter your server settings. You will still be able to simultaneously configure Address Book and iCal for use with Microsoft Exchange.

Mail
- Autodiscovery and account configuration with support for simultaneous setup of Address Book and iCal
- Reading & writing Messages, Notes, and To Do's

iCal
- Scheduling events.
- Checking recipient and room availability.

Address Book
- Adding contacts and groups.
- Verifying data is consistent in Outlook and Address Book.
- Exchange support is available in "Address Book" (version 5.0) not "Address Book (Leopard.)"

Known Limitations in Microsoft Exchange Support:

Mail
- Working offline is not yet supported so actions performed while offline will not be sent to the server when the account goes online.
- Event invitations, delegation authorizations and some other types of messages are not currently displayed.
- Some characters in messages that are moved from another account to a Microsoft Exchange account may be replaced with '=' characters.
- Account information for Microsoft Exchange will be lost if a user's home directory is shared between Snow Leopard and Leopard.
- Undo / redo is not fully supported.

iCal
- Creating calendars on Microsoft Exchange accounts is not yet supported.
- Calendar and task folders must have the same permissions for delegation.

Address Book
- Syncing a Microsoft Exchange account doesn't always work as expected.
- Smart groups are not fully supported.
- Some menu and preference items are missing or disabled.
- Undo / redo is not fully supported.
- Adding a search result from the global address list to your local contacts will prevent future searches from returning results until Address Book is restarted.

Multicore - Grand Central

Dispatch queues and event sources are now reference counted via retain/release API. Blocks submitted to a queue for asynchronous execution retain the target queue until they have executed. Dispatch event sources also retain the target queue to which they submit their event handler Blocks.

The dispatch_call() and dispatch_call_wait() API have been removed. Two new interfaces have been introduced: dispatch_async() and dispatch_sync(). Callbacks should now be expressed as nested blocks.

Accessors to three "well-known" global concurrent queues with a priority level (high, default, low) have been added. This allows Blocks to be executed asynchronously without the application needing to create a specific queue for them. Blocks submitted to the high priority queue will be executed before blocks submitted to the default priority queue, and so on. Dispatch queues created by the application may also set their priority level.

Dispatch event sources now report error codes via the the dispatch_event_t argument to event handler Blocks. Applications should check the event for errors using the dispatch_event_get_error() API inside their event handler Blocks. Once a dispatch event source reports an error, it will never deliver any additional event handler Blocks and may be released by the application.

Monitoring the same underlying Grand Central object (i.e. process identifier, signal, file descriptor) from multiple dispatch event sources may have unreliable results.

Running the following two commands in Terminal will provide additional information Grand Central:
headerdoc2html -o ~/Desktop/libdispatch_core /usr/include/dispatch/core.h
headerdoc2html -o ~/Desktop/libdispatch_events /usr/include/dispatch/events.h

Multicore - Blocks

Syntax Changes
The existing syntax of bracketing "by reference" variables between '|' (bar) symbols is deprecated and will be removed. There is a new form of storage available, __block storage, and it is on par with register, auto, and static for local variables. The new syntax is:

void foo() {
__block int i = 0; // "i" lives in block storage
void (^myblock)(void) = ^{ printf("is is now: %d\n", ++i); };
myblock(); // i is now: 1
myblock(); // i is now: 2
}

A Block literal (e.g. ^{ ... }) is implemented as the address of a stack local data structure that represents the Block. The stack local data structure has scope of the enclosing compound statement. The following, for example, should be avoided:

void bar() {
void (^blockArray[3])(void); // an array of 3 block references
for (int i = 0; i < 3; ++i) {
blockArray = ^{ printf("hello, %d\n", i); }; // INCORRECT: block literal scope is "for loop"
}
}

It is now possible to use a global Block literal

int GlobalInt = 0;
int (^getGlobalInt)(void) = ^{ return GlobalInt; };

C++ support
- Blocks are now supported in C++ and ObjC++
- Within a member function references to member variables and functions are via an implicitly imported "this" pointer and thus appear mutable. During a Block_copy the literal value of the "this" pointer is copied so memory management of the object must be done carefully.
- A stack based C++ object that is referenced within a block must have a const copy constructor. During a Block_copy a const copy will be made into the heap storage. Two known issues are there is no destructor called on the stack based block const copy and under Garbage Collection the heap based destructor is not invoked.

Debugger support
- It is possible to set breakpoints and single step into Blocks.
- Blocks can now be invoked from within a gdb session:

$ invoke-block myblock 10 20

- Note that C strings need to be passed in the form "\"this string\""

- Block storage starts out on the stack just like Blocks do and is copied to the heap when either a Block_copy (or in ObjC a -copy message) is performed. Thus, the address of a __block variable can change over time.

64-bit Kernel

The early 2008 models of the Mac Pro, 15" and 17" MacBook Pro and Xserve can be used for 64-bit kernel development. Audio and AirPort are now enabled on these on these testing configurations. In SnowLeopard, the 64-bit kernel is is used by default on the Xserve and the Mac Pro and MacBook Pro systems can be booted into the 64-bit kernel in one of two ways:

1) Temporarily boot into the 64-bit kernel by holding down "6" and "4" while powering on the machine
2) Run `sudo nvram boot-args="arch=x86_64" ` to set the 64-bit kernel as your default kernel, and append any other debugging flags you may need, such as "debug=0x144". To revert back to the 32-bit kernel as the default, you can run `sudo nvram -d boot-args`.

This seed contains the necessary support for porting kexts to 64-bit and developers are strongly encouraged to do so.

Known Limitations in the 64-bit kernel:

- Shark does not work on the 64-bit kernel.
- Sleep / wake and power management is not currently supported. It is recommend that you disable sleep in System Preferences.
- Graphics acceleration is not yet supported which may cause programs which require graphics acceleration to run incorrectly.
- Some behavior which was previously unsupported, such as modifying a collection while enumerating it, and attempting to modify a kext's __TEXT segment, now results in diagnostic kernel panics.

Finder

Almost all user facing applications in Mac OS X are written in Cocoa with the exception of a select few. Finder, one of the oldest Carbon applications in the system, is being transitioned to Cocoa for SnowLeopard and much progress has been made in this seed. Please report any issues you find with the new Cocoa pieces of Finder.

Default Gamma Changes

To better meet the needs of digital content producers and consumers, the default display gamma has been changed from 1.8 to 2.2 in Snow Leopard. Applications that override the deftault and assume a gamma 1.8 setting may have different onscreen and printed output than they did in previous releases of Mac OS X. Please report any visual differences that you encounter.

Mac OS X Installer

Details can be found in the "Developer Preview Information" document in the "Instructions" folder.

Additional Changes Since the WWDC Seed

- Split view support has been added to Terminal and tab support has been enhanced with a contextual menu and the ability to create new tabs by double clicking.
- The Basic Security Module (BSM) audit code now uses OpenBSM version 1.1a1http://www.trustedbsd.org/openbsm.html <http://www.trustedbsd.org/openbsm.html>
- Snow Leopard uses Java SE 6 for all Java applications and applets.

System Preferences

The System Preferences application will now run with garbage collection enabled under 64-bit. However, in order to support legacy pref panes, when run under 32-bit garbage collection will be disabled. This means that your preference pane code must support both retain-release and garbage collection modes -- similar to a framework that supports garbage collection.

Automator

- Automator can now export Workflows as Services.
- New Find and Filter Actions have been made available.

International Preferences

- Added support for Uighur.
- Added support for calendars in the following languages: Chinese, Coptic, Ethiopic, Ethiopic Amete Alem, Indian National, Persian, Republic of China.

High Level Toolbox

- Added constants for F16-F19 glyphs and a way to specify resolution of images in menus.
- Added API to specify rounded corners in menus (a la contextual menus.)

IPSec/racoon

- The default racoon.conf file will now look for additional include files in /var/run/racoon instead of /private/etc/racoon/remote.
- /private/etc/racoon/remote/anonymous.conf is only to be used as a reference and will no longer be supported.

Pluggable Authentication Modules (PAM)

- Linux-PAM has been replaced by OpenPAM.
- Modules developers may need to adjust to some API changes. In particular, the misc_conv function has been superseded by openpam_ttyconv(3); and pam_std_option has been superseded by openpam_get_option(3).
- It is recommended that modules be recompiled for Snow Leopard and installed with the file name “pam_<module>.so.2”.

OpenSSL

- OpenSSL has been updated to version 0.9.8i. http://www.openssl.org/news/changelog.html <http://www.openssl.org/news/changelog.html>
- Previous versions (0.9.7l for Intel and PowerPC; and 0.9.6l for PowerPC only) of the OpenSSL libraries are included for runtime binary compatibility only and cannot be used at link time.
- If a project’s build system references a specific version of OpenSSL, the project may need to be updated. For example, if an Xcode project references “/usr/lib/libcrypto.0.9.7.dylib” or “-lcrypto.0.9.7”, this should be changed to “/usr/lib/libcrypto.dylib” or “-lcrypto” respectively.

Apple HFS+ File Compression

- File compression has been added to the HFS+ file system.
- Compression was designed to be used with Apple System and Application files that are normally read-only/updatable. These files are not normally copied by users, however, if they are, the copies will be expanded to their normal size.
- This is not a new file system format and does not require volumes to be repartitioned.

Developers who write disk utility programs may need to recognize these files exist, and some details about how they are implemented. In the st_flags field of the stat struct of a compressed file, bit SF_COMPRESSED will be set to indicate that the file is compressed. In addition to this bit, the compression information will be stored in invisible extended attributes "com.apple.decmpfs" and possibly the "com.apple.ResourceFork". On a Tiger or Leopard system, these files will show up as zero length and have the indicated extended attributes. On Snow Leopard, the file's length will show up as its uncompressed length and these extended attributes will be invisible to your software. Thus, any copy program will see proper information to make an uncompressed copy of the data on Snow Leopard. This is to prevent the creation of unreadable compressed files on other file systems and external disks that may make their way back to previous OSes. As always, it is not advised to copy system files from one OS release to previous ones.

*Additional information for most technologies listed here can be found by selecting "Documentation" in the Xcode Help menu.

Known Limitations

Installing Mac OS X

- Some machines may panic during the reboot after installation. The install has still suceeded so please reboot again.
- Some users may hit a crash in the Mac OS X Installer. If you see this please save your installer log for a report to Apple, reboot and then attempt the install again.
- Third-party keyboards are not recommended for use in this seed and may result in an Mac OS X Installer crash.
- To install on a MacBook Air you will need to either use the USB drive or perform a remote install over ethernet. Remote installs over AirPort are not functioning in this seed.
- After installing on a MacBook Air you will need to restart before you can use AirPort.
- This seed is not supported on the Fall 2008 MacBooks and MacBook Pros.

Finder

- Keyboard navigation does not always work as expected.
- Finder sometimes crashing after burning a CD.
- System applications and files may not be correctly copied via Finder. Please use command line tools such as 'ditto' or 'cp' to workaround this.
- Browsing the system Trash in column view may cause Finder to consume significant amounts of the CPU.

Java

- Applets using Java Advanced Imaging (JAI) crash on launch.
- Java Applets fail to load in Firefox.
- Adobe Version Cue v 3.1 fails to launch as it looks for J2SE 5.0, rather than running under Java SE 6.

iChat

- PDF / Keynote documents are blank in iChat Theater.
- iChat Theater may crash when sharing a movie or a picture.
- iChat may not immediately connect when launched.

- Please ensure that the batteries for any attached Bluetooth are sufficiently charged. The warning dialog about low batteries may log you out of your session.
- Selecting a contact with a stored birth date will leave Address Book in an unusable state. Quit and relaunch Address Book to work around this. If you need to view or edit contacts with stored birth dates use "Address Book (Leopard)". If the first contact in "Address Book" has a stored birthdate you will need to remove the birth date using using "Address Book (Leopard)" or only browse contacts with "Address Book (Leopard)".
- Attempting to include the AppKit framework header file NSMenuItem.h (or any header file such as Cocoa.h which imports NSMenuItem.h) in a project which uses gcc 4.0 will result in a compile-time failure. You can work around this by editing /System/Library/Frameworks/AppKit.framework/Headers/NSMenuItem.h, and on line 17, removing "DEPRECATED_IN_MAC_OS_X_VERSION_10_6_AND_LATER", leaving just "@protocol NSMenuItem;". If you are using the 10.6 SDK, you will also need to similarly edit /Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSMenuItem.h.
- Keychain syncing may result in errors and it is reccomended that Keychain Syncing be disabled in this seed.
- Some systems with ATI graphics cards may show pink flashes when using the built in iSight camera.
- Selecting "Paper Feed" or "Cover Page" in the printer options may result in an inability to print.
- Some auto-mounted network shares may become unavailable after a period of time.
- On a 64-bit system QuickTime Pro Registration via the QuickTime Preference Pane is unavailable until relaunch System Preferences in 32-bit.
- Users with ATI Radeon HD 2600 graphics cards may see graphics corruption when dragging windows.
- Atempting to print to a postscript printer may result in errors.
- Mobile accounts (portable home directories) cannot be created with this seed.
- iDisks display an error upon the initial connection attempt, but clicking on the disk again will successfully bring up your iDisk contents.
- Ink is not reccomended for use in this seed.
 
Snow Leopard is new software technologies that enhance the performance of Intel Macs.

Actually the last part of that isn't true. While I'm sure there are some processor-specific optimizations being made, the vast majority of code in OSX is architecture independent. Most optimization opportunities in software are algorithmic improvements, not tuning instruction choice or ordering.
 
[snip] NDA text


you really forgot one very important part :

THE INFORMATION CONTAINED IN THIS MESSAGE IS UNDER NON-DISCLOSURE

Like this is the first time seed notes were made public. :rolleyes:

Now distributing a link to the software, that I would agree with saying something about. :apple:
 
I strongly disagree with the abandonment of PowerPC. Apple should name it SNOW JOB 10.6

Leopard is a bug-ridden dog on PowerPC Macs compared to Tiger and now Apple's answer to that is QUALITY and PERFORMANCE enhancements to INTEL-ONLY Macs? Ridiculous. I'm surprised there isn't already a class action lawsuit over this. The description alone of Snow Leopard almost sounds like an admission of guilt that Apple got it wrong the first go-round with Leopard!

Leopard has to be Steve Jobs' biggest reality distortion field con job yet and I've been using Apple products since 1983.

And yes, I own plenty of PowerPC Macs, and I don't feel that Leopard is a quality product even on my Dual 1.8 G5. We won't even get into how buggy Leopard is on an 867MHz Powermac G4 Quicksilver or my MDD, but yes, Apple certified Leopard to run on those machines. Why is it that my MDD Mac freezes inexplicably from time to time in Leopard or my G5 kernel panics when each of these machines runs flawlessly for months without a reboot in Tiger. Riddle me THAT Batman!

Sometimes I feel like its as if Apple barely even tested the PowerPC version of Leopard much and most of the bug fixes I see happening in each update appear to be more Intel-related and Snow Leopard only confirms my early suspicions.

I'm sure if Steve Jobs had his way, he'd have put a PowerPC chip in a coffin at last year's MacWorld. But, I'm sure the lawyers would have warned him Apple would see the mother of all lawsuits and public outrage.

Sure, the PC switchers, iPhone, & iPod sales are making the paychecks now for Apple now, but the people who spent upwards of $4000 on then overpriced PowerPC equipment just a couple short years ago kept Apple in business during the previous decade when things looked bleak.

Show a little compassion Steve Jobs and fix Leopard for all supported Macs, NOT just the ones you currently sell! Is that really too much to ask? I don't think so.

I totally agree with you. However, Snow Leopard should be the end of the line for PPC. After that point it's kind of silly.
 
"Snow Leopard uses Java SE 6 for all Java applications and applets." Well it's about time! lets hope it's Java update 10, and gets released in Feb with some quad core MBP's :)

No sign of ZFS...
 
They're arguably the most stunning of all the big cats. They are also endangered species (there are only ~5,000 left in the wild), so hopefully “green” Apple donates some money to saving them from some of the profits they make selling an operating system baring their name.

I see Adobe, IBM, Microsoft and Nikon on the list of donors for the Snow Leopard Trust, but not Apple.

Regardless, where's the creativity? First Leopard, now Snow Leopard? Remarkably creative.
 
"Snow Leopard uses Java SE 6 for all Java applications and applets." Well it's about time! lets hope it's Java update 10, and gets released in Feb with some quad core MBP's :)

No sign of ZFS...
I believe ZFS is only being added to Snow Leopard Server, not the client edition. ZFS will mean little to most end users.
 
I strongly disagree with the abandonment of PowerPC. Apple should name it SNOW JOB 10.6

Leopard is a bug-ridden dog on PowerPC Macs compared to Tiger and now Apple's answer to that is QUALITY and PERFORMANCE enhancements to INTEL-ONLY Macs? Ridiculous. I'm surprised there isn't already a class action lawsuit over this. The description alone of Snow Leopard almost sounds like an admission of guilt that Apple got it wrong the first go-round with Leopard!

Leopard has to be Steve Jobs' biggest reality distortion field con job yet and I've been using Apple products since 1983.

And yes, I own plenty of PowerPC Macs, and I don't feel that Leopard is a quality product even on my Dual 1.8 G5. We won't even get into how buggy Leopard is on an 867MHz Powermac G4 Quicksilver or my MDD, but yes, Apple certified Leopard to run on those machines. Why is it that my MDD Mac freezes inexplicably from time to time in Leopard or my G5 kernel panics when each of these machines runs flawlessly for months without a reboot in Tiger. Riddle me THAT Batman!

Sometimes I feel like its as if Apple barely even tested the PowerPC version of Leopard much and most of the bug fixes I see happening in each update appear to be more Intel-related and Snow Leopard only confirms my early suspicions.

I'm sure if Steve Jobs had his way, he'd have put a PowerPC chip in a coffin at last year's MacWorld. But, I'm sure the lawyers would have warned him Apple would see the mother of all lawsuits and public outrage.

Sure, the PC switchers, iPhone, & iPod sales are making the paychecks now for Apple now, but the people who spent upwards of $4000 on then overpriced PowerPC equipment just a couple short years ago kept Apple in business during the previous decade when things looked bleak.

Show a little compassion Steve Jobs and fix Leopard for all supported Macs, NOT just the ones you currently sell! Is that really too much to ask? I don't think so.

I agree with you, and so does my Quad G5!
 
Thanks!

These are what I think is significant for end users:

Finder
Almost all user facing applications in Mac OS X are written in Cocoa with the exception of a select few. Finder, one of the oldest Carbon applications in the system, is being transitioned to Cocoa for SnowLeopard and much progress has been made in this seed. Please report any issues you find with the new Cocoa pieces of Finder.
Confirmation.

- Snow Leopard uses Java SE 6 for all Java applications and applets.
This is interesting because at the moment Java 6 is 64bit only on Leopard:
So this means one of two things:
[1] Apple has written Java SE 6 support for 32 bit Intel machines
[2] Snow Leopard won't support 32 bit Intel machines

Default Gamma Changes
To better meet the needs of digital content producers and consumers, the default display gamma has been changed from 1.8 to 2.2 in Snow Leopard. Applications that override the deftault and assume a gamma 1.8 setting may have different onscreen and printed output than they did in previous releases of Mac OS X. Please report any visual differences that you encounter.
2.2 = Windows Gamma. Interesting.

Automator
- Automator can now export Workflows as Services.
And no doubt appear in the services menu — neat!


Apple HFS+ File Compression
- File compression has been added to the HFS+ file system.
- Compression was designed to be used with Apple System and Application files that are normally read-only/updatable. These files are not normally copied by users, however, if they are, the copies will be expanded to their normal size.
- This is not a new file system format and does not require volumes to be repartitioned.
One of the reasons Snow Leopard it will take up less space on the Hard Disk.


Then from the limitations we can establish what they are working on:
- Ink is not reccomended for use in this seed.
Ink (which is for handwriting recognition). Commonly used on tablets, tablets hey…
 
isn't snow leopard just a name that has been dubbed until the official announcement? or am i wrong here?
 
I totally agree with you. However, Snow Leopard should be the end of the line for PPC. After that point it's kind of silly.

Now there we totally agree. Snow Leopard should be the end of the line for PowerPC and logically so. Instead Apple is spending its resources on the iPhone and screwing over it's longtime faithful base and that's the real reason they have to concentrate on Intel-only.

And yes, Snow Leopard is a bad naming choice and will continue to invoke the wrath of PowerPC Mac owners regardless of what some here say.

I find it astounding that there are people here on this site that think that PowerPC Leopard users DON'T deserve STABILITY and PERFORMANCE in Leopard, the 2 KEY marketing points put forth by Apple in Snow Leopard. All of this junk science talk about Snow Leopard having only Intel-specific technologies at work is annoying and untrue and most people realize that. I'm certain Apple will keep a secret PowerPC build of Snow Leopard somewhere hidden away too just like they did previously with Intel builds. Don't be so naive.

Shame on some of you for your Kool aid drinking snobbery.

All Apple would have to do is make a statement that Leopard and Snow Leopard would co-exist in concurrent development separately BUT that the stability and performance improvements in Snow Leopard would be available in PowerPC Leopard upgrades. No such statement has been made that I'm aware of. That would diminish the pain of spending $129 on an operating system that Apple now admits publicly is not stable or has performance issues. I'm using Apple's and Steve Jobs' own words. If they don't want them used against them, then they shouldn't stick their feet in their mouths. It's just that simple.
 
I strongly disagree with the abandonment of PowerPC. Apple should name it SNOW JOB 10.6

Leopard is a bug-ridden dog on PowerPC Macs compared to Tiger and now Apple's answer to that is QUALITY and PERFORMANCE enhancements to INTEL-ONLY Macs? Ridiculous. I'm surprised there isn't already a class action lawsuit over this. The description alone of Snow Leopard almost sounds like an admission of guilt that Apple got it wrong the first go-round with Leopard!

Leopard has to be Steve Jobs' biggest reality distortion field con job yet and I've been using Apple products since 1983.

And yes, I own plenty of PowerPC Macs, and I don't feel that Leopard is a quality product even on my Dual 1.8 G5. We won't even get into how buggy Leopard is on an 867MHz Powermac G4 Quicksilver or my MDD, but yes, Apple certified Leopard to run on those machines. Why is it that my MDD Mac freezes inexplicably from time to time in Leopard or my G5 kernel panics when each of these machines runs flawlessly for months without a reboot in Tiger. Riddle me THAT Batman!

Sometimes I feel like its as if Apple barely even tested the PowerPC version of Leopard much and most of the bug fixes I see happening in each update appear to be more Intel-related and Snow Leopard only confirms my early suspicions.

I'm sure if Steve Jobs had his way, he'd have put a PowerPC chip in a coffin at last year's MacWorld. But, I'm sure the lawyers would have warned him Apple would see the mother of all lawsuits and public outrage.

Sure, the PC switchers, iPhone, & iPod sales are making the paychecks now for Apple now, but the people who spent upwards of $4000 on then overpriced PowerPC equipment just a couple short years ago kept Apple in business during the previous decade when things looked bleak.

Show a little compassion Steve Jobs and fix Leopard for all supported Macs, NOT just the ones you currently sell! Is that really too much to ask? I don't think so.

Bad RAM?
 
I personally use 10.4.11 and am exceedingly happy with it...

Well, there you go then. You don't even need 10.5 or 10.6.

I think it is perfectly fair that my PPC Macs are really good machines running 10.4 and my Intel Macs are really good machines running 10.5.
10.4 is ideal for PPC and 10.5 is ideal for Intel. Apple are still updating both frequently. I'm happy.

To make it as clean and speedy as possible I wish for 10.6 to be Intel only.

People who crave for a constant focus on backwards compatability should take a look at Windows and see how it has cribbled all posibilites for real innovation, OS elegance and speed. The 10.6-vision is a chance for Apple to do something MS will never be able to do.
 
I think it is perfectly fair that my PPC Macs are really good machines running 10.4 and my Intel Macs are really good machines running 10.5.
10.4 is ideal for PPC and 10.5 is ideal for Intel. Apple are still updating both frequently. I'm happy.

Except for "security" updates (which have legal implications if Apple doesn't fix known problems), Apple has not updated 10.4 in nearly a year.

I run Leopard on my ancient G4 Sawtooth tower and it does quite well.
 

Seems to me bad RAM would cause a similar problem in Tiger or Panther, wouldn't you think ?

Never had issues with these 2 Macs (MDD & G5) until Leopard & yes, they are RAM maxed out. I'm not an expert, but I suspect that the constant Spotlight indexing of changed files is the culprit as these machines are workhorses that are intensely used with lots of disk activity & RAID setups unlike some other Macs I have which run Leopard without crashing but still slowly & more minor bugginess.

Oddly enough, I also have an unsupported SAWTOOTH G4 MAC that does not freeze or kernel panic in Leopard, but obviously its slow as molasses and virtually unusable for anything but email and generic tasks which is all its used for.

If Apple is admitting that new features is not the point of Snow Leopard, but just stability and performance enhancements, then it's like they're admitting Leopard is buggy from the start. Therefor denying PowerPC users these stability and performance enhancements is a mistake in my opinion.

PowerPC users are not complaining that they're not getting new Snow Leopard features or Intel-specific tech. No, to the contrary, we just want the same stability and performance enhancements wherever there is not Intel specific issues. Last I checked Cocoa is NOT Intel specific tech and there could easily be (and probably will be a secret) PowerPC build of Snow Leopard regardless of whether Apple releases it or not.

Apple is making a big mistake in both the requirements for Snow Leopard and the marketing of it and leaving a bad taste in the mouths of LOTS of people who spent $129 on Leopard not expecting that a year later, Apple would announced Leopard Part II, the Leopard that works and is stable and performance driven but NO YOU CANNOT HAVE IT!

That's sad and bad PR in my opinion.
But no, I won't be going out next year and buying Vista machines to cut off my hand to save a finger to spite myself either. Don't worry! :D
But I'm disappointed in Apple's handling of this BIGTIME. :(
 
waah waah waah

ATTENTION WHINERS:

if tiger works better than leopard for you, by all means KEEP ON USING IT.

no one is making you upgrade... either hardware *OR* software. you already own all the technology you originally paid for (and then some), and presumably you've gotten years' worth of value out of it by now.

<sarcasm>

what?!?!? you mean apple is going to KEEP ADVANCING their products... and their newest tech may not work on my 20 year old mac se/30?!? HOW DARE THEY!?!?!?!? MADNESS! OUTRAGE! CLASS ACTION LAWSUIT!!!!! etc etc etc!!!!

</sarcasm>

i hope some of you realize how ridonkulous you sound.

oh, and by the way, snow leopard is a rad name :D

that is all.
 
Is Mac OS X 10.6 going to be 64-bit-only? Eliminating PPC code is a no-brainer, but what about the x86 code? If we are just talking about the Mac then I would think the 32-bit code would also get removed, but the iPhone and iPod touch use the "same" OS X code so maybe not. Then again, Apple could develop 32-bit code solely for the iPhone/iPod touch and 64-bit code for the Mac so Mac OS X 10.6 and on will be 64-bit "clean".
The iPhone/iPod has a ARM cpu not a X86 one.
 
Because Apple cripples features and burns bridges as a stated business model, this discussion about complaining about one OS style or another really boils down to resource allocation decisions within Apple.

The primary driver for OS creation is hardware update cycles. Bug fixes are to some degree an entirely different track. The decision to dump OS9 support was so the nacent new portable OS could be started with existing resources along side then well underway OSX development.

Now PPC support will be forsaken to allow Snow Leopard which is essentially multi-core centric and 64 bit heavy OS.

I for one have consistently advocated for a small division at Apple to keep working on older releases just to maintain ongoing bug fixes and security updates and awareness for follow-on Mac and OS models. That is not asking much. It would make tons of people happy, not impact new computer sales very much since they are new feature driven, and could provide a small revenue stream.

Happy customer bases are good things.

Rocketman
 
If Apple is admitting that new features is not the point of Snow Leopard, but just stability and performance enhancements, then it's like they're admitting Leopard is buggy from the start. Therefor denying PowerPC users these stability and performance enhancements is a mistake in my opinion.

PowerPC users are not complaining that they're not getting new Snow Leopard features or Intel-specific tech. No, to the contrary, we just want the same stability and performance enhancements wherever there is not Intel specific issues. Last I checked Cocoa is NOT Intel specific tech and there could easily be (and probably will be a secret) PowerPC build of Snow Leopard regardless of whether Apple releases it or not.

Apple is making a big mistake in both the requirements for Snow Leopard and the marketing of it and leaving a bad taste in the mouths of LOTS of people who spent $129 on Leopard not expecting that a year later, Apple would announced Leopard Part II, the Leopard that works and is stable and performance driven but NO YOU CANNOT HAVE IT!

That's sad and bad PR in my opinion.
But no, I won't be going out next year and buying Vista machines to cut off my hand to save a finger to spite myself either. Don't worry! :D
But I'm disappointed in Apple's handling of this BIGTIME. :(

Leopard (PPC and Intel) is great and continues to improve, until at least next June (WWDC'09). SL is not just "Leopard with bugfixes" as you imply. SL is "better" and "different" in a number of ways.

I'm guessing you didn't go to WWDC this year to actually hear Bertrand Serlet give the answers to your concerns. If you did, you'd understand what they're trying to do and why they're not 'sticking it' to PPC users. SL is the next leap and it's not Apple's fault that you don't know why yet. He told everyone in attendance.

Bottom line: You're wrong, but noone here can tell you exactly how or why because of the NDA. Next year, go to WWDC so you can make more a informed judgement.
 
ZFS is important to end user!

I believe ZFS is only being added to Snow Leopard Server, not the client edition. ZFS will mean little to most end users.

I highly disagree. ZFS for the end user means: 1.) speed (much faster I/O performance) 2.) efficiency with file storage to take up less hard drive space (only remembers the main file, and the changes, doesn't make multiple files with changes added like HFS+) 3.) Disk Compression - seems like HFS+ will have this too in 10.6.

I feel ZFS will be roled out like HFS+. It started in the Server edition, then trickled down to client 10.2.8 I think. Something like that anyway. I bet there will not be a GUI controls for ZFS until 10.7. ZFS will totally be an option though in 10.6, eventually if not at first.

I'm surprised with the Cocoa rewrite of the Finder, Apple isn't more gung-ho about integrating ZFS - after all a lot of the work that needs to be done is GUI level stuff according to the forge. I would love to have ZFS integration at the level OpenSolaris has... particularly the Nautilus version with its Time Capsule. Rewrite Time Machine to take advantage of snapshots... talk about efficiency and saving space.... TM is a huge waste of efficiency and space! As an end user, I want all that back!
 
Leopard (PPC and Intel) is great and continues to improve, until at least next June (WWDC'09). SL is not just "Leopard with bugfixes" as you imply. SL is "better" and "different" in a number of ways.

I'm guessing you didn't go to WWDC this year to actually hear Bertrand Serlet give the answers to your concerns. If you did, you'd understand what they're trying to do and why they're not 'sticking it' to PPC users. SL is the next leap and it's not Apple's fault that you don't know why yet. He told everyone in attendance.

Bottom line: You're wrong, but noone here can tell you exactly how or why because of the NDA. Next year, go to WWDC so you can make more a informed judgement.

Without breaking the NDA, any thoughts on ZFS? Perhaps a prediction on the direction Apple will take with that technology in Snow Leopard, or does it really look like they will just copy features and add them to HFS+? Finally, do you think MacWorld will have any words on ZFS?

(sorry to be annoying, this is just a feature I really want and have no way of making informed observations. forums seem to be my only release. :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.