Though it was fixed within a week whereas the Windows delayed-write failure has still not been fixed.
Heh, Fixed in 10.5.1 :)
I've been using a mac daily for more than one year now and I gotta say this, people are unreasonably forgiving to the mac. I mean, it's cute and all but it's got its own issues.
I upgraded to Leopard and if people think vista wasn't ready when it came out, consider that Leopard is much smaller release than vista and the amount of bugs I encountered in Leopard makes me feel like this cat isn't ready either.
Title of a blog post in a few years: "And that's how I ruined the move function in Leopard." :P
Only partially fixed, you mean:
"Leopard users hoped that a free maintenance update (OSX 10.5.1), released on Thursday, November 15, would fix the issue, but Apple's statement accompanying the update is too vague to give a definitive answer. With regard to data loss, it states that "... a potential data loss issue when moving files across partitions ..." has been fixed, but moving files across hard drives is not addressed. Personally, I wouldn't want to bet my important data on that statement."
I hate this kind of gratuite trashing. You should at least check if it hasn't really been address before stating it. Or just keep your topics on what your blog is about, you know: 'Unit Testing, Agile Development, Architecture, Team System & .NET'
bastian.
My apologies. Please let me know what you'd like me to write about next. In fact, it would be great if you could also send me the full text of the post you'd like me to write.
You are free to get your money back if this blog has not lived to its SLA.
Talk about whatever you want. Just give arguments when you are criticizing (if calling stupid an OS can be called criticizing) something if you want to be given some credit. Can you reproduce a data loss on different hard drives after applying the patch or are you just interpreting the note at your will?
PS: BTW, I am no OSX fan either, after having having used it for about 3 years.
I'm not sure what your comment about drives versus partitions is supposed to mean.
In Unix (and perhaps windows?) when you "move" a file within the same partition, nothing much happens besides updating the file table - the actual data stays in place.
To move across partitions, the physical data has to be copied onto the new partition - whether that happens to be the same physical drive or a different one is not important.
Of course your partition may not be a single drive; it might be RAID'ed across multiple drives. Or maybe its a loopback device stored as a file within some other partition.
The OS doesnt care, the process it undertakes is exactly the same - all it knows is the destination is a different partition, so the same-partition-shortcut can not be taken.