Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Snow Leopard is a lame name. They should have come up with a new cat name like they always used to. There are plenty they could have chosen from. I liked having a new cat each time. This is just a variation on an old cat. I want a new cat.

I think Snow Leopard was the most perfect name they could have chose. That is because visually and feature-wise, Snow Leopard will look the same as Leopard. Apple has stated that Snow Leopard will not include any new features. The changes are mostly under the hood. So since Snow Leopard will basically be an improved version of Leopard, it is the perfect name choice.
 
He said that he excluded his download folder. Imagine if you downloaded lots of movies and TV shows before you move them to a NAS drive on your home network, Time Machine would pick up every one of them and create backups and you'd have hundreds of gigs in no time.

Personally I'm not sure how I'm supposed to benefit from Time Machine. If I want to keep a file, I keep it. If I want to get rid of a file, I get rid of it. The purpose of backup, for me anyway, is to have an exact shadow copy in case the hard drive goes. Time Machine does the opposite, it skips certain files and instead it accumulates tons of old garbage that only exists in that location, so if your TM drive goes you lose all that stuff anyway. In a worst case scenario, it teaches people to be careless about throwing files away, and then return a couple of months later only to find that TM has pushed those old files off the cliff. It's like replacing the trash can with an entire garbage dump. Nice interface though.

I disagree. It works very well, keeps several revisions of any given file (if it changes) and if you have a RAID1 external drive, is fine for redundancy. The old garbage gets deleted as TM needs space; I don't see what the problem there is. If you delete something large that you're sure you don't want, highlight it and click delete all versions, if you're that concerned about space.

I've got a $110 Lacie HD, 1TB, with 3 months of backups. That includes virtual machines (which I really don't need to back up), 20GB of iTunes, 15GB of video, 10GB of pictures, etc.

TM is much better than the back up in XP, which creates this monolithic single .bkf file. Not sure what's in Vista (hopefully it's better) because I've never stomached Vista long enough as a main desktop to make a backup. Haven't played with 7 yet in that regard.
 
10.5.7 reported no issues with last seed-so it could be out any day now

SL is a service pack-but it wont be free-it may cost $75 to add (update) it to Leopard, and $129 for those without

I firmly remember reading from an authoritative source that SL would be out late Summer.
Authoritative because I suddenly gave up hope that it was no longer a rumor-and thus let go of hope for a June release


This is all speculation of course
 
10.5.7 reported no issues with last seed-so it could be out any day now

SL is a service pack-but it wont be free-it may cost $75 to add (update) it to Leopard, and $129 for those without

I firmly remember reading form an authoritative source that SL would be out late Summer.
Authoritative because I suddenly gave up hope that it was no longer a rumor-and thus let go of hope for a June release

I'd be happy to pay $129 for what SL offers, but I'd be even happier if it was only $75.
 
I guess I chose my words incorrectly. I wasn't criticizing it, merely suggesting a few improvements. I have many clients that use Time Machine and there are certain precautions about proper utilization to improve effectiveness. For someone who works on their system, backups can be large as their working data becomes significant over time. This is especially true for photographers and designers who work with large amounts of data (such as RAW file formats). Otherwise, it is a solid system.
It somehow goes without saying that if you produce GBs of data every day and repeatedly change them that you exclude them. It is almost a reflex to do so, one does not even have to think about it. And if you created ten or more GB of data per day you'll certainly in a situation where dealing with it has become second nature.
But 99.9% of all people are not in this situation.
 
He said that he excluded his download folder. Imagine if you downloaded lots of movies and TV shows before you move them to a NAS drive on your home network, Time Machine would pick up every one of them and create backups and you'd have hundreds of gigs in no time.
There is one big misjudgement in this reasoning.
- First, TM only keeps hourly backups for 24 hours, so lets say the backup from last Monday will reflect either the very first or the very last backup on that day (I never bothered to find out, or rather never bothered to remember when I had found it out). So for once, if your large files are not on your computer at around midnight (but on your NAS) they will not persist in TM for longer than 24 hours.
- Second, TM keeps daily backups only for a month and weekly backups forever. Which day is chosen to represent the week, I have no idea, lets assume it is Sunday. If on Sundays at midnight all large files are on the NAS already, none of these will stay in TM for more than a month.
To phrase it differently, to ensure that a file stays permanently in TM it has to stay in one place for at least one week (3.5 days gives it a 50% chance and so on). Formulated the other way around, if a file stays less than one day in one place, chances are pretty low that it will end up in TM permanently.
 
Personally I'm not sure how I'm supposed to benefit from Time Machine. If I want to keep a file, I keep it. If I want to get rid of a file, I get rid of it. The purpose of backup, for me anyway, is to have an exact shadow copy in case the hard drive goes. Time Machine does the opposite, it skips certain files and instead it accumulates tons of old garbage that only exists in that location, so if your TM drive goes you lose all that stuff anyway.
I have three independent backups, I have never needed them because of drive failure (but I had two backup drives go bad). But I need them maybe once a month because I either deleted something by accident or modified a file and want to go back to an earlier version. About once or twice a year I do something really stupid like deleting files referenced in Aperture or deleting whole folders with thousands of files.
TM is not an archive unless you place it on a redundant system and give it infinite space. It is a safety net with a lot of layers.
 
I have three independent backups, I have never needed them because of drive failure (but I had two backup drives go bad). But I need them maybe once a month because I either deleted something by accident or modified a file and want to go back to an earlier version. About once or twice a year I do something really stupid like deleting files referenced in Aperture or deleting whole folders with thousands of files.
TM is not an archive unless you place it on a redundant system and give it infinite space. It is a safety net with a lot of layers.
OK. Well, I'll evaluate TM in a few weeks when I get a couple of Macs for work. I bought a WD MyBook Studio 2 TB for the desktop and a 1 TB for the laptop, and I figured i'd use then for both Time Machine and Windows backup and split them 1 TB/1 TB and 500 GB/500 GB, respectively.

I've only tried TM briefly on my iMac to see what it did, but it seemed like a silly concept to back up loads of redundant files, plus the files are uncompressed so I suspect the disk will fill up in no time... but I hope I'll be proven wrong. I can see one good use for it; I won't have to do incremental backups in Flash for fear of ending up with a corrupted FLA file, which has happened a couple of times.
 
Possibly but I don't see it happening. I've been using SL since the first build and I've seen vast improvements in each new seed.

There might even be an internal build that's running a lot better than the Dev. seeds but Apple is keeping it closed due to unreleased upcoming hardware.;)

Too true. That was my next thought ;)
 
OSX names

Before Snow Leopard I used to wonder whether OSX versions were named after big cats or German tanks.
 
10.5.7 reported no issues with last seed-so it could be out any day now

SL is a service pack-but it wont be free-it may cost $75 to add (update) it to Leopard, and $129 for those without

I firmly remember reading from an authoritative source that SL would be out late Summer.

Authoritative because I suddenly gave up hope that it was no longer a rumor-and thus let go of hope for a June release

This is all speculation of course

Absolutely wrong on 2 counts:

1 - SL is NOT a Service Pack; it's a new version of the OS with a vast number of under-the-hood improvements and features; 10.5.x updates are the equivalent of service packs (which added, for example, extra view modes for Stacks and so on);

2 - Apple has NEVER released a new OS X with upgrade paths; it's gonna cost $129 to buy it, nothing more, nothing less, independently of which OS version you have on your Mac.
 
No it is not mainly a stability update. You think things like GrandCentral and OpenCL just happen over night with a few lines of code? There are few flashy and easy to market items.


I'm not denying that there are new features...I'm just pointing out the reasoning for the name. The name is a variation on Leopard because this OS was designed as a variation of Leopard. The fact that stability is being marketed over features is exactly the reason that the name of the OS (which is for marketing purposes) reflects that.

There is one big misjudgement in this reasoning.
- First, TM only keeps hourly backups for 24 hours, so lets say the backup from last Monday will reflect either the very first or the very last backup on that day (I never bothered to find out, or rather never bothered to remember when I had found it out). So for once, if your large files are not on your computer at around midnight (but on your NAS) they will not persist in TM for longer than 24 hours.
- Second, TM keeps daily backups only for a month and weekly backups forever. Which day is chosen to represent the week, I have no idea, lets assume it is Sunday. If on Sundays at midnight all large files are on the NAS already, none of these will stay in TM for more than a month.
To phrase it differently, to ensure that a file stays permanently in TM it has to stay in one place for at least one week (3.5 days gives it a 50% chance and so on). Formulated the other way around, if a file stays less than one day in one place, chances are pretty low that it will end up in TM permanently.

TM chooses EVERY hour for the daily backup and EVERY day for the weekly backup. If you add a file at noon, it is backed up by TM, then you delete it and add a new file at 1pm, it is backed up by TM. Your daily backup will include both items.
 
Absolutely wrong on 2 counts:

1 - SL is NOT a Service Pack; it's a new version of the OS with a vast number of under-the-hood improvements and features; 10.5.x updates are the equivalent of service packs (which added, for example, extra view modes for Stacks and so on);

2 - Apple has NEVER released a new OS X with upgrade paths; it's gonna cost $129 to buy it, nothing more, nothing less, independently of which OS version you have on your Mac.

Agreed a new kernel and task scheduler Grand Central is not a service pack. I think Service Pack is the most overused and misunderstood feature.

I think $129 would be unfortunate simply for the fragmentation it would bring to OS X. Snow Leopard is certainly going to be a great forward thinking OS but I don't know if the dual core Intel Mac owner is going to get a sense that they "really" need Snow Leopard.
 
One question that I still have regarding 10.6 is: why are the applications still compiled for both x86 and PPC architectures? Apple has (much to the ire of some) killed PPC support for the OS; hence, why would there any reason to compile for an architecture that cannot be used anymore?
 
One question that I still have regarding 10.6 is: why are the applications still compiled for both x86 and PPC architectures? Apple has (much to the ire of some) killed PPC support for the OS; hence, why would there any reason to compile for an architecture that cannot be used anymore?

There's no reason. So if anyone is claiming 10.6 support yet they have PPC binaries they have nothing to test in Snow Leopard for PPC.
 
Does this mean *not* fat binaries anymore - no PPC/x86?

There's no reason. So if anyone is claiming 10.6 support yet they have PPC binaries they have nothing to test in Snow Leopard for PPC.

Note that in June 2008, applications were tagged with "(Universal)". In Jan 2009, that is no longer the case.

Jan 2009:

2009-02-21sl.jpg



June 2008:

3.jpg



Also notice that the most of the new apps are *much* smaller.

If I'm mis-reading these screen captures, please explain.
 
Note that in June 2008, applications were tagged with "(Universal)". In Jan 2009, that is no longer the case.

Jan 2009:

Also notice that the most of the new apps are *much* smaller.

If I'm mis-reading these screen captures, please explain.

Nope I don't think you're misreading at all. Apple must have pulled the extraneous code from their apps.

Next i'm wondering how much extra the 32-bit/64-bit binaries are.
 
I'm not denying that there are new features...I'm just pointing out the reasoning for the name. The name is a variation on Leopard because this OS was designed as a variation of Leopard. The fact that stability is being marketed over features is exactly the reason that the name of the OS (which is for marketing purposes) reflects that.

Wrong. A Snow Leopard is a completely different species of cat from a Leopard, and OS X Snow Leopard is a new OS. And a new kernel is not going to be as stable (atleast in the initial releases) as a tried and tested one. The main user-visible improvement in Snow Leopard will be better performance as it exploits hardware parallelism better.

Agreed a new kernel and task scheduler Grand Central is not a service pack. I think Service Pack is the most overused and misunderstood feature.

I think $129 would be unfortunate simply for the fragmentation it would bring to OS X. Snow Leopard is certainly going to be a great forward thinking OS but I don't know if the dual core Intel Mac owner is going to get a sense that they "really" need Snow Leopard.

Maybe, but that is equally true for the upgrade from XP to Vista, for example. Not everyone upgrades immediately no matter how compelling the new release may appear. For example, I didn't upgrade from Panther to Tiger as Panther was good enough for what I was doing. I upgraded only when Leopard came out. However, I do plan to upgrade to Snow Leopard once it comes out.
 
Maybe, but that is equally true for the upgrade from XP to Vista, for example. Not everyone upgrades immediately no matter how compelling the new release may appear. For example, I didn't upgrade from Panther to Tiger as Panther was good enough for what I was doing. I upgraded only when Leopard came out. However, I do plan to upgrade to Snow Leopard once it comes out.

I know ..upgrade timeframes are a personal decision for us all. I just notice that with each OS revision it becomes easier and easier for developers to create fantastic apps.

How many developers are working on Quicken? 20 maybe? I don't know. There's one guy behind MoneyWell. I'm absolutely amazed at what a single developer can accomplish today regardless of platform.

A lot of people fail to realize that the cool new stuff Apple delivers today in the OS often won't manifest in many apps until the following year or their next major revision. Leopard's been out for a year and a half and Apple just delivered iLife and iWork updates with more Leopard support (like Core Animation).

Though I expect the upcoming Final Cut Studio, Logic Studio and Aperture updates to support Snow Leopard the latter half of this year it won't be until their 2010 revisions that we begin to see more Snow Leopard features turned on an optimized.

If I'm a developer I'm going to make a pact with my users. I would break legacy support off faster but in turn I would make my upgrades cheaper.

Imagine a developer today with a userbase of %40 Tiger users %60 Leopard. Well that developer is going to have to develop with 3 OS version in mind. Tiger for Legacy...Leopard for current and Snow Leopard for the future.

If his Tiger userbase is small he/she then needs to make the decision on whether to move to Leopard and Snow Leopard development which is certainly going to be easier.

John that wasn't aimed at you I'm just on my soapbox here. I want to see every Intel Mac user on Leopard at minimum and if Apple can entice these people to quickly migrate to Snow Leopard we all benefit because our apps will be more stable and secure.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.