Dude needs some cheese with that whine.

Since when? My install took 10 mins.


What OS installer does?


So...


This I agree with, but I haven't had an update go bad on me yet..


So..


Thats a third party problem then...


Whine some more..


Same as other OSs.. so..


Thats a unix limitation


Um.. alright.. I am sure that the list of things it does well far exceeds this little list of nonesense. Looks like he had to dig hard to find anything bad. Let me guess, he still uses OS9 since its a "good os"....?

that was one worthless letter....

Who?

I've read MANY issues of MacWorld and other publications both on and off the net, and I know LOTS of writers, but I never heard of this guy.

Mike

In OS 9 you can drag a window by the border. Yes, he likes OS 9 better. Didn't you read the letter?

He was probably using pearpc to install OS X. Mine takes 15 minutes at most, and this is on an aging Powerbook G4 667 (gigabit ethernet).

Oh and regarding system updates, is archive and install too hard for him?

OSX's installer isn't fast, it's true. But good God; three days?! What machine was he trying to use?

RAM is not in the habit of reporting its manufacturer to the OS, last I checked, so the only way to detect this RAM would be to run actual tests on it. Thorough testing can take hours to run on systems with large amounts of RAM. The most thorough method known to date -the Major March- can take upwards of a week. This man is complaining about the install taking too long, and he wants to add in RAM testing?

Tough cookies. Anyone here remember OSX 10.0, then this installation phase was not performed? Although this is a minor annoyance, it results in performance gains which were more than worth it.

Only if you don't back up your Home folder. Everybody sing, to the tune of "If You're Happy And You Know It":

Alternatively, you can use the installer's "Archive And Install" option, which preserves user data.

Why is he actually trying to manage these things, as though they were INITs under OS9? Would he prefer that they be rolled into the kernel, creating stability and security issues?

This is a problem with that program, not with OSX. Apple is known to work with big developers to help fix bugs; they should be taking advantage of this.

This was true up until OS8, as well as OSX. No one complained then.

Actually, filenames can contain question marks, even on standard Unix, though they require a bit of hoop-jumping if you intend to use them in the Terminal.

There are only two characters which cannot appear in OSX filenames: slash (/) and colon (. Of these, the colon wasn't allowed in OS9 either, because it was used to separate folder names when dealing with file paths. The same is true of the slash in OSX. All other characters are allowed.

Fixing permissions does surprisingly little; although it can help on rare occasions, it is mostly voodoo. What Apple really needs to do is fix its Installer to keep permissions from being messed up in the first place.

If you read the letter, he was trying to change the names of some of the audio devices he has attached or something like that. I have no knowledge about anything audio, so that's the part I didn't understand too well.

Probably because it reminds people of Sept 11th.

That letter should be a wake-up call for many of you die-hard apologists. Seriously.
By the way, the OP forgot to mention another point:

� Permissions Suck.

Quote from the linked article:


Well, he needs to go and read up on the concept of domains. How many networked environments has this person maintained? Seperating the Library directories is a Good Thing(TM).

http://developer.apple.com/document...ts/Domains.html

here we go again with you.

Permissions are the reason OS X will never be prey to viruses like Windows is.

Adapt or die.

I guess because the TETENAL doesn't agree with permissions being a nuisance (like the vast majority of us). Permissions were integrated into HFS long before OS X, it is not something that magically appeared in OS X. (AFAIK Copland was a multi-user OS, too.)

If you take a look at what happens in the windows world, a big big weakness is XP Home Edition is the lack of permissions. Every virus/worm compromises the whole machine.

viruses spyware etc. suck.


locks on doors SUCK. they keep me from opening doors easily.

That you can't use / in filenames The actual filename of your hypothetical file there contains no slashes. It is actually called

What:does:he:mean?

Yeah, I read the letter that guy wrote. I don't think Steve Jobs is going to lose too much sleep over it.

Slashes in the Finder will be converted to semicolons in the Terminal and vice versa. In OS 9 days, folders were separated by semicolons whereas in all Unixoid OSes, they use slashes. M$ uses backslashes.

However, you are wrong about one thing: in Unix, you can use "/" in file names, but it makes things cumbersome and often many scripts don't work. So they are practically not used in Linux, etc.

That depends on which OS layer you are in. In the POSIX layer, you are correct. In other layers the slashes will be there/

Wow stuff like this is such a waste of time to even read. What do you OS 9 advocates and complainers hope to achieve? For Steve jobs to redesign the entire OS to stasify a group of like 20 ignorant people? Some how I just don't see it happening. Instead of wasting peoples time by complaining about OS 10 you should be spending time creating programs for OS 9, since no one else will.

I'd say it's more like satisfying the 50% or more of the userbase that's still comfortably using their Macs, waiting for OS X to be ready for them to switch platforms. It's not like those Powermacs are flying off the shelves, are they?

as if they were ever flying off the shelves? You're such an interesting person, it seems like you argue for the sake of arguing.



Edited by Detrius. Watch the personal attacks.

This statement fails on its face:

1) Claiming that those who have not switched are only doing so because they are waiting for OS X without any evidence to back up the claim is facile. Many people have not switched because many people will never switch until they buy a new machine; I know several people still using OS 9 because it is fine for their needs. These are not technically inclined people, so as long as the machine works, they're happy. If you have any data to back up your claim, I would like to see it;

2) 4Q2004 Power Mac sales were only off 4% compared to 3Q2004 sales. iMac sales were up 147% from 3Q2004. As all are OS X machines, your logic fails once again.

Ecxept that he's wrong about 9/10ths of it.

As opposed to insecure systems? Just because you're ignorant about computer security does not mean that computers should be insecure.

Nothing to see here - move along...

You must have been reading some other post because I never said that you couldn't use / in UNIX filenames but rather you can't use / in Mac OS X filenames.

And you can't.

I just named a file with a forward slash in the Finder just now. Am I hallucinating?