MAC or PC — Page 8

TV’s Frink said:

yhwx said:

imperialscum said:

This thread is one big embarrassment… MAC is a PC, you idiots.

Yeah, we all know that. We’re using PC in a more specific sense.

And Mac is never, never in all caps.

MAC

So how did I do that?

Terribly.

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Hopefully I’ll get to discuss why file name extensions are stupid.

I think you’re confused on the meaning of “hopefully.”

It’s really interesting, I promise.

Sounds fishy.

Back in the day, Macs had a unique way to identify file types: Type/Creator codes. In the resource fork of a file, the OS would store the type of file (basically the file name extension) and the creator of the file (the application you used to create the file). This system has many advantages, including the most important one (to me, at least): You can name the file whatever you want, and it’ll still open correctly.

The impossibility of this is what makes file name extensions terrible: You can’t give the user control of their data. Coding the file type in the file name is a fundamentally bad idea. Would you put the date created in the file name? Size? Metadata? You’d probably say no. These are all file metadata that are as important as the file type. But, no, file type is a-ok because that’s how it’s always been outside of the Mac world! That’s just how things are, isn’t it?

It is, but it doesn’t have to be this way.

Apple solved the problem again eleven years ago with Uniform Type Identifiers. This system has solves many major problems with type/creator codes, file name extensions, and MIME types. It first solves specificity problems: Type/Creator codes are limited to four characters, which is small enough to have collisions with other file types. (This is also a problem with file name extensions, as file name extensions can theoretically be as long as possible, Microsoft & Co. refuse to break from the EIGHT.THREE file naming convention of yesteryear) It also doesn’t need a registration with a standards committee, which is a problem with MIME types. There’s also many more benefits and intricacies to Uniform Type Identifiers, which you’ll have to see the link I linked above to get all the juicy details on.

Now, Apple has been far from perfect in this arena. Back around the transition from Classic Mac OS to Mac OS X (Windows users: Think of the transition from Windows 9x to XP, but much bigger), Apple basically abandoned Type/Creator codes, making file name extensions the required form of file type identification. This lasts until today, which many Apple users (such as myself) are grumbly about. (Along with the lack of a new file system — but that’s on the way!)

I don’t know why you posted this, given the fact that there was no way I’d ever read it.

It’s not that full of technical jargon. The only problem is that it’s a few paragraphs long, which seems to be beyond your attention span.

My attention span only cares about things that matter.

File name extensions do matter! Don’t you want to name files whatever you want without having that pesky three character identifier at the end?

No.

I don’t get how you can’t care. That limitation is technically offensive to me.

I’m not you, despite your attempts to be a MiniFrink.

I DO NOT attempt to be a MiniFrink. That is just a blatantly wrong misconception.

File name extensions are anti-consumer. You are a consumer. You should be against this.

Consumers suck.

I should have said user. The operating system should yield to the user unless the user will do something stupid.

TV’s Frink said:

yhwx said:

Dek Rollins said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Hopefully I’ll get to discuss why file name extensions are stupid.

I think you’re confused on the meaning of “hopefully.”

It’s really interesting, I promise.

Sounds fishy.

Back in the day, Macs had a unique way to identify file types: Type/Creator codes. In the resource fork of a file, the OS would store the type of file (basically the file name extension) and the creator of the file (the application you used to create the file). This system has many advantages, including the most important one (to me, at least): You can name the file whatever you want, and it’ll still open correctly.

The impossibility of this is what makes file name extensions terrible: You can’t give the user control of their data. Coding the file type in the file name is a fundamentally bad idea. Would you put the date created in the file name? Size? Metadata? You’d probably say no. These are all file metadata that are as important as the file type. But, no, file type is a-ok because that’s how it’s always been outside of the Mac world! That’s just how things are, isn’t it?

It is, but it doesn’t have to be this way.

Apple solved the problem again eleven years ago with Uniform Type Identifiers. This system has solves many major problems with type/creator codes, file name extensions, and MIME types. It first solves specificity problems: Type/Creator codes are limited to four characters, which is small enough to have collisions with other file types. (This is also a problem with file name extensions, as file name extensions can theoretically be as long as possible, Microsoft & Co. refuse to break from the EIGHT.THREE file naming convention of yesteryear) It also doesn’t need a registration with a standards committee, which is a problem with MIME types. There’s also many more benefits and intricacies to Uniform Type Identifiers, which you’ll have to see the link I linked above to get all the juicy details on.

Now, Apple has been far from perfect in this arena. Back around the transition from Classic Mac OS to Mac OS X (Windows users: Think of the transition from Windows 9x to XP, but much bigger), Apple basically abandoned Type/Creator codes, making file name extensions the required form of file type identification. This lasts until today, which many Apple users (such as myself) are grumbly about. (Along with the lack of a new file system — but that’s on the way!)

I don’t know why you posted this, given the fact that there was no way I’d ever read it.

It’s not that full of technical jargon. The only problem is that it’s a few paragraphs long, which seems to be beyond your attention span.

My attention span only cares about things that matter.

File name extensions do matter! Don’t you want to name files whatever you want without having that pesky three character identifier at the end?

What’s wrong with file name extensions? You can still name the file whatever you want (pretty much), there’s just a period followed by the file type afterward. What’s wrong with being able to see the file type? What’s “pesky” about it?

My point is that file metadata should never, ever come into contact with the user space that is the file name, and that includes file types.

And you do realize that the file name extensions can be turned off, right?

They’re still there. It’s just a shoving under the rug, which is not a solution.

Once the ignore function comes back, people can shove your posts under a rug, even though they’re still there.

SOLUTION!

Nah, it’s not a solution.

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true.

Prove it.

MAC is never accepted anywhere in the Apple community.

The fact that such a thing exists proves that Tyrphanax is right.

Tyrphanax said:

yhwx said:

Dek Rollins said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Hopefully I’ll get to discuss why file name extensions are stupid.

I think you’re confused on the meaning of “hopefully.”

It’s really interesting, I promise.

Sounds fishy.

Back in the day, Macs had a unique way to identify file types: Type/Creator codes. In the resource fork of a file, the OS would store the type of file (basically the file name extension) and the creator of the file (the application you used to create the file). This system has many advantages, including the most important one (to me, at least): You can name the file whatever you want, and it’ll still open correctly.

The impossibility of this is what makes file name extensions terrible: You can’t give the user control of their data. Coding the file type in the file name is a fundamentally bad idea. Would you put the date created in the file name? Size? Metadata? You’d probably say no. These are all file metadata that are as important as the file type. But, no, file type is a-ok because that’s how it’s always been outside of the Mac world! That’s just how things are, isn’t it?

It is, but it doesn’t have to be this way.

Apple solved the problem again eleven years ago with Uniform Type Identifiers. This system has solves many major problems with type/creator codes, file name extensions, and MIME types. It first solves specificity problems: Type/Creator codes are limited to four characters, which is small enough to have collisions with other file types. (This is also a problem with file name extensions, as file name extensions can theoretically be as long as possible, Microsoft & Co. refuse to break from the EIGHT.THREE file naming convention of yesteryear) It also doesn’t need a registration with a standards committee, which is a problem with MIME types. There’s also many more benefits and intricacies to Uniform Type Identifiers, which you’ll have to see the link I linked above to get all the juicy details on.

Now, Apple has been far from perfect in this arena. Back around the transition from Classic Mac OS to Mac OS X (Windows users: Think of the transition from Windows 9x to XP, but much bigger), Apple basically abandoned Type/Creator codes, making file name extensions the required form of file type identification. This lasts until today, which many Apple users (such as myself) are grumbly about. (Along with the lack of a new file system — but that’s on the way!)

I don’t know why you posted this, given the fact that there was no way I’d ever read it.

It’s not that full of technical jargon. The only problem is that it’s a few paragraphs long, which seems to be beyond your attention span.

My attention span only cares about things that matter.

File name extensions do matter! Don’t you want to name files whatever you want without having that pesky three character identifier at the end?

What’s wrong with file name extensions? You can still name the file whatever you want (pretty much), there’s just a period followed by the file type afterward. What’s wrong with being able to see the file type? What’s “pesky” about it?

My point is that file metadata should never, ever come into contact with the user space that is the file name, and that includes file types.

Why?

Because the file name is the user’s space. They should be able to put whatever they want in there.

Dek Rollins said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true.

Prove it.

MAC is never accepted anywhere in the Apple community.

The fact that such a thing exists proves that Tyrphanax is right.

Not to mention the fact that they’re apparently super particular about how Macintosh Apple Computer is abbreviated.

TV’s Frink said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true. MAC is never accepted anywhere in the Apple community.

That’s because the Apple community is stupid. The evidence being they like Apples.

Dek Rollins said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true.

Prove it.

MAC is never accepted anywhere in the Apple community.

The fact that such a thing exists proves that Tyrphanax is right.

Why do you hate Apple and anybody that uses their products so much?

yhwx said:

Tyrphanax said:

yhwx said:

Dek Rollins said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Hopefully I’ll get to discuss why file name extensions are stupid.

I think you’re confused on the meaning of “hopefully.”

It’s really interesting, I promise.

Sounds fishy.

Back in the day, Macs had a unique way to identify file types: Type/Creator codes. In the resource fork of a file, the OS would store the type of file (basically the file name extension) and the creator of the file (the application you used to create the file). This system has many advantages, including the most important one (to me, at least): You can name the file whatever you want, and it’ll still open correctly.

The impossibility of this is what makes file name extensions terrible: You can’t give the user control of their data. Coding the file type in the file name is a fundamentally bad idea. Would you put the date created in the file name? Size? Metadata? You’d probably say no. These are all file metadata that are as important as the file type. But, no, file type is a-ok because that’s how it’s always been outside of the Mac world! That’s just how things are, isn’t it?

It is, but it doesn’t have to be this way.

Apple solved the problem again eleven years ago with Uniform Type Identifiers. This system has solves many major problems with type/creator codes, file name extensions, and MIME types. It first solves specificity problems: Type/Creator codes are limited to four characters, which is small enough to have collisions with other file types. (This is also a problem with file name extensions, as file name extensions can theoretically be as long as possible, Microsoft & Co. refuse to break from the EIGHT.THREE file naming convention of yesteryear) It also doesn’t need a registration with a standards committee, which is a problem with MIME types. There’s also many more benefits and intricacies to Uniform Type Identifiers, which you’ll have to see the link I linked above to get all the juicy details on.

Now, Apple has been far from perfect in this arena. Back around the transition from Classic Mac OS to Mac OS X (Windows users: Think of the transition from Windows 9x to XP, but much bigger), Apple basically abandoned Type/Creator codes, making file name extensions the required form of file type identification. This lasts until today, which many Apple users (such as myself) are grumbly about. (Along with the lack of a new file system — but that’s on the way!)

I don’t know why you posted this, given the fact that there was no way I’d ever read it.

It’s not that full of technical jargon. The only problem is that it’s a few paragraphs long, which seems to be beyond your attention span.

My attention span only cares about things that matter.

File name extensions do matter! Don’t you want to name files whatever you want without having that pesky three character identifier at the end?

What’s wrong with file name extensions? You can still name the file whatever you want (pretty much), there’s just a period followed by the file type afterward. What’s wrong with being able to see the file type? What’s “pesky” about it?

My point is that file metadata should never, ever come into contact with the user space that is the file name, and that includes file types.

Why?

Because the file name is the user’s space. They should be able to put whatever they want in there.

Not being able to use nine pretty rarely-used characters in a filename has never once been an issue in my life.

I can prove the MAC capitalization because everybody who holds power (Apple and prominent Apple writers for many years) will never use MAC.

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Hopefully I’ll get to discuss why file name extensions are stupid.

I think you’re confused on the meaning of “hopefully.”

It’s really interesting, I promise.

Sounds fishy.

Back in the day, Macs had a unique way to identify file types: Type/Creator codes. In the resource fork of a file, the OS would store the type of file (basically the file name extension) and the creator of the file (the application you used to create the file). This system has many advantages, including the most important one (to me, at least): You can name the file whatever you want, and it’ll still open correctly.

The impossibility of this is what makes file name extensions terrible: You can’t give the user control of their data. Coding the file type in the file name is a fundamentally bad idea. Would you put the date created in the file name? Size? Metadata? You’d probably say no. These are all file metadata that are as important as the file type. But, no, file type is a-ok because that’s how it’s always been outside of the Mac world! That’s just how things are, isn’t it?

It is, but it doesn’t have to be this way.

Apple solved the problem again eleven years ago with Uniform Type Identifiers. This system has solves many major problems with type/creator codes, file name extensions, and MIME types. It first solves specificity problems: Type/Creator codes are limited to four characters, which is small enough to have collisions with other file types. (This is also a problem with file name extensions, as file name extensions can theoretically be as long as possible, Microsoft & Co. refuse to break from the EIGHT.THREE file naming convention of yesteryear) It also doesn’t need a registration with a standards committee, which is a problem with MIME types. There’s also many more benefits and intricacies to Uniform Type Identifiers, which you’ll have to see the link I linked above to get all the juicy details on.

Now, Apple has been far from perfect in this arena. Back around the transition from Classic Mac OS to Mac OS X (Windows users: Think of the transition from Windows 9x to XP, but much bigger), Apple basically abandoned Type/Creator codes, making file name extensions the required form of file type identification. This lasts until today, which many Apple users (such as myself) are grumbly about. (Along with the lack of a new file system — but that’s on the way!)

I don’t know why you posted this, given the fact that there was no way I’d ever read it.

It’s not that full of technical jargon. The only problem is that it’s a few paragraphs long, which seems to be beyond your attention span.

My attention span only cares about things that matter.

File name extensions do matter! Don’t you want to name files whatever you want without having that pesky three character identifier at the end?

No.

I don’t get how you can’t care. That limitation is technically offensive to me.

I’m not you, despite your attempts to be a MiniFrink.

I DO NOT attempt to be a MiniFrink. That is just a blatantly wrong misconception.

File name extensions are anti-consumer. You are a consumer. You should be against this.

Consumers suck.

I should have said user. The operating system should yield to the user unless the user will do something stupid.

Users suck. Long live MCP.

You’re basically saying that you suck.

yhwx said:

I can prove the MAC capitalization…

I know you can prove that. You just used it. In fact, we already proved it by using before.

Tyrphanax said:

yhwx said:

Tyrphanax said:

yhwx said:

Dek Rollins said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Hopefully I’ll get to discuss why file name extensions are stupid.

I think you’re confused on the meaning of “hopefully.”

It’s really interesting, I promise.

Sounds fishy.

Back in the day, Macs had a unique way to identify file types: Type/Creator codes. In the resource fork of a file, the OS would store the type of file (basically the file name extension) and the creator of the file (the application you used to create the file). This system has many advantages, including the most important one (to me, at least): You can name the file whatever you want, and it’ll still open correctly.

The impossibility of this is what makes file name extensions terrible: You can’t give the user control of their data. Coding the file type in the file name is a fundamentally bad idea. Would you put the date created in the file name? Size? Metadata? You’d probably say no. These are all file metadata that are as important as the file type. But, no, file type is a-ok because that’s how it’s always been outside of the Mac world! That’s just how things are, isn’t it?

It is, but it doesn’t have to be this way.

Apple solved the problem again eleven years ago with Uniform Type Identifiers. This system has solves many major problems with type/creator codes, file name extensions, and MIME types. It first solves specificity problems: Type/Creator codes are limited to four characters, which is small enough to have collisions with other file types. (This is also a problem with file name extensions, as file name extensions can theoretically be as long as possible, Microsoft & Co. refuse to break from the EIGHT.THREE file naming convention of yesteryear) It also doesn’t need a registration with a standards committee, which is a problem with MIME types. There’s also many more benefits and intricacies to Uniform Type Identifiers, which you’ll have to see the link I linked above to get all the juicy details on.

Now, Apple has been far from perfect in this arena. Back around the transition from Classic Mac OS to Mac OS X (Windows users: Think of the transition from Windows 9x to XP, but much bigger), Apple basically abandoned Type/Creator codes, making file name extensions the required form of file type identification. This lasts until today, which many Apple users (such as myself) are grumbly about. (Along with the lack of a new file system — but that’s on the way!)

I don’t know why you posted this, given the fact that there was no way I’d ever read it.

It’s not that full of technical jargon. The only problem is that it’s a few paragraphs long, which seems to be beyond your attention span.

My attention span only cares about things that matter.

File name extensions do matter! Don’t you want to name files whatever you want without having that pesky three character identifier at the end?

What’s wrong with file name extensions? You can still name the file whatever you want (pretty much), there’s just a period followed by the file type afterward. What’s wrong with being able to see the file type? What’s “pesky” about it?

My point is that file metadata should never, ever come into contact with the user space that is the file name, and that includes file types.

Why?

Because the file name is the user’s space. They should be able to put whatever they want in there.

Not being able to use nine pretty rarely-used characters in a filename has never once been an issue in my life.

You’re not getting my point. (purposefully, probably) I was complaining about file name extensions, which is different from character use. Also, it’s just technically offensive to not allow a thing that is totally possible to allow and will cause basically no problems at all.

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true. MAC is never accepted anywhere in the Apple community.

That’s because the Apple community is stupid. The evidence being they like Apples.

Dek Rollins said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true.

Prove it.

MAC is never accepted anywhere in the Apple community.

The fact that such a thing exists proves that Tyrphanax is right.

Why do you hate Apple and anybody that uses their products so much?

See: this thread.

I never said that Apple was perfect. in fact, I pointed out an instance where I was annoyed at Apple. You’re the ones who seem to think that PCs are perfect and that Macs are the devil.

Dek Rollins said:

yhwx said:

I can prove the MAC capitalization…

I know you can prove that. You just used it. In fact, we already proved it by using before.

I guess you’ll just never understand. Would you like it if I called Microsoft Microshit?

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true. MAC is never accepted anywhere in the Apple community.

That’s because the Apple community is stupid. The evidence being they like Apples.

Dek Rollins said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true.

Prove it.

MAC is never accepted anywhere in the Apple community.

The fact that such a thing exists proves that Tyrphanax is right.

Why do you hate Apple and anybody that uses their products so much?

See: this thread.

You’re the ones who seem to think that PCs are perfect and that Macs are the devil.

We never said that. We said that Macs are trash compared to non-Mac PCs. And that Macs aren’t real computers.

Dek Rollins said:

yhwx said:

TV’s Frink said:

yhwx said:

TV’s Frink said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true. MAC is never accepted anywhere in the Apple community.

That’s because the Apple community is stupid. The evidence being they like Apples.

Dek Rollins said:

yhwx said:

Dek Rollins said:

yhwx said:

Neglify said:

yhwx said:

Neglify said:

M.A.C.

If you could do that again in the correct way, I would like your comment more.

Sorry I know you hate abbreviations. Macintosh Apple Computer. Better?

No. Mac is an accepted abbreviation.

“Mac” is a shortening of “Macintosh”. “MAC” (or M.A.C. or M*A*C) is an abbreviation of the phrase “Macintosh Apple Computer.”

There.

No, it is not. None of your post is true.

Prove it.

MAC is never accepted anywhere in the Apple community.

The fact that such a thing exists proves that Tyrphanax is right.

Why do you hate Apple and anybody that uses their products so much?

See: this thread.

You’re the ones who seem to think that PCs are perfect and that Macs are the devil.

We never said that. We said that Macs are trash compared to non-Mac PCs. And that Macs aren’t real computers.

Your argument has no legs to stand on. I can give specific reasons why Windows and most non-Mac PCs have inherent design flaws that are anti-user and make no sense at all. You people, on the other hand, got notta.

yhwx said:

Dek Rollins said:

yhwx said:

I can prove the MAC capitalization…

I know you can prove that. You just used it. In fact, we already proved it by using before.

I guess you’ll just never understand. Would you like it if I called Microsoft Microshit?

I don’t have an estranged loyalty to Microsoft, so I wouldn’t really care. Especially considering that Microsoft is rather crappy.

(Also, capitalizing the latter two letters in Mac isn’t nearly as insulting as your Microsoft example.)