Linked by Thom Holwerda on Sun 25th Nov 2007 11:12 UTC, submitted by trinitrotolueen
Mac OS X "This is something I never thought I'd hear myself say - or maybe I should say, see myself type - about an Apple operating system: Mac OSX Leopard was released before it was ready. This operating system needed more testing on more systems with more hardware, and especially, more software configurations. The days of Apple computers operating with just the Mac OS and Adobe Photoshop installed, and practically nothing else to speak of, are long gone, and Apple knows this as well as anyone. This operating system was not properly beta tested, and Apple's customers are paying for it, with lost productivity and inoperative computers."
Thread beginning with comment 286645
To read all comments associated with this story, please click here.
Problems with the article
by wocowboy on Sun 25th Nov 2007 12:51 UTC
wocowboy
Member since:
2006-06-01

The better part of the article is about two problems, one that is supposedly fixed in 10.5.1 but evidently the author doesn't believe it is, although he offers no evidence that it wasn't.

The file management problem is easily avoided by COPYING a file from one location to another instead of MOVING. From the desktop, the mv command is not even available when you right-click a file, only Copy is available. Seems the only way you get into trouble is by using the Terminal instead of doing things graphically. I would think it's mostly advanced users that are familiar with Unix commands who use the terminal to move files around in this manner.

In any case, mv-ing a file across drives or partitions is MUCH more risky than cp-ing in ANY instance. Simple basic file-management procedures take care of it. NEVER mv a file across partitions or drives! Do a cp, check the integrity of the moved file, and then rm the original file if the copy is OK. Problem solved! And the world keeps turning.

The other matter, the so-called "blue screen of death" is mainly a "hang screen" that occurs because of the APE problem. The reboot "hangs" and the screen that results happens to be blue. My iMac has a blue screen as part of normal bootup. This is different from Windows BSOD which has all sorts of gobbledygook text on it. I will grant that an indication from Apple that if a blue screen displays for more than 20 minutes that there might be a problem would be good of them to do.

This author suffers from the same problem as other "X-Company is failing" authors. They assume and posit that if there are posts in support forums about problems, then by logic those problems are affecting ALL users and that it indicates that X's products are going down the tubes quality-wise, and that X is trying to suppress criticism, so X must be evil, and they and everyone else should never support X's products again. Whew!

There are always problems with new OS's, and we are all beta testers in the end. Given time, bugs are found out and fixed. The vast majority of 10.5 users are probably "ignorant" and are having no problems. I seem to be one of them. So be it!

Reply Score: 5

RE: Problems with the article
by prince_seth on Sun 25th Nov 2007 16:41 in reply to "Problems with the article"
prince_seth Member since:
2006-11-22

in any case, mv-ing a file across drives or partitions is MUCH more risky than cp-ing in ANY instance. Simple basic file-management procedures take care of it. NEVER mv a file across partitions or drives! Do a cp, check the integrity of the moved file, and then rm the original file if the copy is OK. Problem solved! And the world keeps turning.

Why? it should not be. If someone wants to MOVE a file then that is what the computer should do. If someone wants to COPY a file, then that is what the computer should to. When I give the command to move a file then the OS should make the requisite integrity checks, and if something is found be wrong then abort the procedure. That is what the computer is for. I mean seriously do I have to check it arithmetic too?

Reply Parent Score: 9

moronikos Member since:
2005-07-06

Imagine if someone (Ballmer/Gates) was using the same justification to excuse a bug in a Microsoft product. MS critics would be having a veritable conniption. I can't see how bugs in moving a file could ever be excused.

Reply Parent Score: 2

RE: Problems with the article
by linumax on Sun 25th Nov 2007 16:59 in reply to "Problems with the article"
linumax Member since:
2007-02-07

"The file management problem is easily avoided by..."

Users' duty to avoid or vendors' duty to fix?

"From the desktop, the mv command is not even available when you right-click a file, only Copy is available. Seems the only way you get into trouble is by using the Terminal instead of doing things graphically."

Drag and Drop

"There are always problems with new OS's, and we are all beta testers in the end. Given time, bugs are found out and fixed. "

Completely agree, all new OSs.

"The vast majority of 10.5 users are probably "ignorant" and are having no problems. I seem to be one of them. So be it!"

Or maybe "tolerant" and there could be a limit to that. For all the good that OSX brings, I can consider a few flaws negligible.

Reply Parent Score: 5

RE: Problems with the article
by nevali on Sun 25th Nov 2007 17:12 in reply to "Problems with the article"
nevali Member since:
2006-10-12

The file management problem is easily avoided by COPYING a file from one location to another instead of MOVING. From the desktop, the mv command is not even available when you right-click a file, only Copy is available. Seems the only way you get into trouble is by using the Terminal instead of doing things graphically. I would think it's mostly advanced users that are familiar with Unix commands who use the terminal to move files around in this manner.


“mv” works fine in Leopard, and always has. The bug affected Finder which moves files when you hold the Option key while dragging and dropping them: if it failed part-way through the move due to the destination becoming unavailable, the source file would be deleted anyway (i.e., it didn't seem to detect that the error had occurred).

It was a stupid bug, and it's been fixed. The fact it could be “avoided” by not doing it isn't really worth the trouble of anybody saying. It's like saying you can avoid getting caught by your car breaking down by riding a bicycle instead.

Reply Parent Score: 5