Live data from Hacker News

Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

store.apple.com

91–100 of 121 posts

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#91
post #63
post #54

Earlier quoted context omitted.

Insanity. Before Leopard, Spotlight was a debacle. After Leopard, it just works. Also: isn't there a whole lot of software you can't install now because Tiger doesn't have Core Animation and isn't LP64? I also wouldn't trust Tiger security on an external network.

Every security update Apple ships for Leopard it also ships for Tiger. And I preferred spotlight in 10.4. In fact, 10.4 was all around a much better OS than 10.5, which was the first update to Mac OS X that felt like a step backwards. Of course, I'll be updating to 10.6 as soon as I can get my hands on it. If nothing else, the promise of a 10.5 that doesn't suck is worth it. To be fair, 10.5 is much better now then w…

You're making the assumptions that every security flaw fixed was:

(a) intentionally, knowingly fixed

(b) disclosed.

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#92
post #83
post #80

Earlier quoted context omitted.

How'd you get 10.6? Were they releasing developer copies?

Sure, but only high level developers got them. However, I was able to learn the final build number from a friend, then I just downloaded it off BT. I have a copy on order but couldn't wait. Call it time-shifting.

Could your instability be attributed to the fact that you might not be running the actual release version (or has been modified in some nefarious way)?

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#93
post #73

You might want to hold off a little while before upgrading, at least until 10.6.1. I upgraded my laptop 3 days ago and since then I've had at least 5 Mail.app crashes, finder a couple of times, and one terminal crash. I did an upgrade install, maybe a clean one is better, but I'm pretty surprised at the instability. Also, if you use Macports, that's not up to speed yet so you'll be doing a lot of fiddling around to g…

I've been using it for a week on a 1st gen MBP (32 bit) and haven't had any crashes.

I don't use Erlang, but I have a lot of packages from MacPorts (mysql5, mercurial, git, svn, xorg, perl5 and python26 ) installed without any problems. The only thing I've tried to build that failed is screen.

I did a clean install, so that may be the difference maker.

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#94
post #17

Earlier quoted context omitted.

The other way to look at this is that Apple gave themselves plenty of buffer to ship.

True, but unlike practically everyone else they didn't allow their work to fit the expanded time available. Everyone builds in buffers and pads their estimates, but few people are able to work to their original true estimate.

True, but unlike practically everyone else they didn't allow their work to fit the expanded time available.

Again, how do we know they didn't account for it when they buffered initially? Maybe they had a different internal timeline (end of aug) vs. an external timeline.

Only way to know is if one is in the Snow Leopard team or has access to that kind of info.

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#95
post #30

Earlier quoted context omitted.

It seems so: http://www.apple.com/macosx/uptodate/

FYI, as of right now, they aren't passing the info from the verification screen to the cart correctly, so you have to use the fax-in form. http://images.apple.com/macosx/uptodate/docs/OSX_HW_UTD_FF.p...

I am having the same problem on the European (Dutch) store as well when I followed the link to computers bought on the Apple store itself.

When I follow the link for computers bought via a reseller it works without a problem.

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#96

Even in marketting copy, Apple's design taste is unrivaled: http://www.apple.com/macosx/ http://www.microsoft.com/windows/windows-7/ I mean seriously, how many levels of tabs are too many? http://www.microsoft.com/windows/windows-7/features/whats-ne...

> Only in marketing, Apple's design taste is unrivaled...

Fixed that for you.

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#97
post #83
post #80

Earlier quoted context omitted.

How'd you get 10.6? Were they releasing developer copies?

Sure, but only high level developers got them. However, I was able to learn the final build number from a friend, then I just downloaded it off BT. I have a copy on order but couldn't wait. Call it time-shifting.

Given that you acquired an illicit copy over the intertubes of unknown origin and authenticity, perhaps you should refrain from commenting?

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#99
post #89
post #85

Earlier quoted context omitted.

Well... Java had them (in almost every OS it ran on) since day 1 too. That puts it a couple years ahead of .NET

I think the point of GCD is that the concept is being brought down to the C, C++, and Objective-C layers, through the introduction of "blocks"... http://www.mikeash.com/?page=pyblog/friday-qa-2008-12-26.htm... http://www.mikeash.com/?page=pyblog/friday-qa-2009-08-14-pra... I agree there's too much marketing hype surrounding GCD, but neither the CLR nor the JVM can jump through that particular hoop.

It's interesting. For the little I have seen (and I was only able to give it a quick glance) it includes syntactic support for multi-threading being built into their Objective-C compiler.

Are they forking the Objective-C compiler?

Re: Mac OS X 10.6 Snow Leopard - Now Available (Delivery on Aug. 28th)

#100
post #94

Earlier quoted context omitted.

True, but unlike practically everyone else they didn't allow their work to fit the expanded time available. Everyone builds in buffers and pads their estimates, but few people are able to work to their original true estimate.

True, but unlike practically everyone else they didn't allow their work to fit the expanded time available. Again, how do we know they didn't account for it when they buffered initially? Maybe they had a different internal timeline (end of aug) vs. an external timeline. Only way to know is if one is in the Snow Leopard team or has access to that kind of info.

> how do we know they didn't account for it when they buffered initially? Maybe they had a different internal timeline (end of aug) vs. an external timeline.

If they were like practically everyone else in this wacky industry, they would be late for the internal timeline but not worry about it because the external timeline is the one that matters. Thus, there would be very little pressure to meet the internal timeline and a lot of pressure to meet the external timeline. Worse, they would wind up being late for the external timeline as well as the internal timeline.

For example, if someone wanted to add a feature to Snow Leopard, the dev team might say "we can't make our internal schedule if we add this." But some product manager would say "well, will you still make the external schedule?" and bang they would start to slip.

If they had an internal schedule and managed to stick to it I believe they are an exception to how software is usually developed.

Post reply on HN