I want this thread and the anime thread to have a beautiful baby abomination together.
Notice that both threads are only kept alive by YHWH’s inability to accept the truth.
It’s your inability to form an intelligent argument for your side.
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.
Then your argument makes even less sense than I thought. I thought you were making the at least somewhat reasonable argument that you should be able to use any character you wanted to name your files, but you were actually saying that it’s bad that a file is labeled a .txt file (for example)? Jesus dude.
Keep Circulating the Tapes.
END OF LINE
(It hasn’t happened yet)
I want this thread and the anime thread to have a beautiful baby abomination together.
Notice that both threads are only kept alive by YHWH’s inability to accept the truth.
It’s your inability to form an intelligent argument for your side.
Your argument is that you don’t like file extensions, that’s the epitome of a shitty argument.
I want this thread and the anime thread to have a beautiful baby abomination together.
Notice that both threads are only kept alive by YHWH’s inability to accept the truth.
He’s actually correct in the anime thread, though.
Army of Darkness: The Medieval Deadit | The Terminator - Color Regrade | The Wrong Trousers - Audio Preservation
SONIC RACES THROUGH THE GREEN FIELDS.
THE SUN RACES THROUGH A BLUE SKY FILLED WITH WHITE CLOUDS.
THE WAYS OF HIS HEART ARE MUCH LIKE THE SUN. SONIC RUNS AND RESTS; THE SUN RISES AND SETS.
DON’T GIVE UP ON THE SUN. DON’T MAKE THE SUN LAUGH AT YOU.
Imma just post Mack memes until this useless non-conversation dies down.
Don’t do drugs, unless you’re with me.
I want this thread and the anime thread to have a beautiful baby abomination together.
Notice that both threads are only kept alive by YHWH’s inability to accept the truth.
It’s your inability to form an intelligent argument for your side.
Your argument is that you don’t like file extensions, that’s the epitome of a shitty argument.
That is not true. It is partly my fault for not saying things about anything other than file name extensions
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.
Then your argument makes even less sense than I thought. I thought you were making the at least somewhat reasonable argument that you should be able to use any character you wanted to name your files, but you were actually saying that it’s bad that a file is labeled a .txt file (for example)? Jesus dude.
I don’t get how people can’t be fired up about this! It’s just technically wrong to do this. Technically offensive, as I said and you don’t seem to get.
Imma just post Mack memes until this useless non-conversation dies down.
Non factual. Almost all of the most powerful applications that people use started or are only on the Mac, with some being on Windows and extremely rarely on Linux.
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.
Then your argument makes even less sense than I thought. I thought you were making the at least somewhat reasonable argument that you should be able to use any character you wanted to name your files, but you were actually saying that it’s bad that a file is labeled a .txt file (for example)? Jesus dude.
I don’t get how people can’t be fired up about this! It’s just technically wrong to do this. Technically offensive, as I said and you don’t seem to get.
Why should people be mad about something that doesn’t affect anyone anywhere in any way?
Keep Circulating the Tapes.
END OF LINE
(It hasn’t happened yet)
Don’t do drugs, unless you’re with me.
Imma just post Mack memes until this useless non-conversation dies down.
Non factual. Almost all of the most powerful applications that people use started or are only on the Mac, with some being on Windows and extremely rarely on Linux.
Not factual.
Keep Circulating the Tapes.
END OF LINE
(It hasn’t happened yet)
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.
Then your argument makes even less sense than I thought. I thought you were making the at least somewhat reasonable argument that you should be able to use any character you wanted to name your files, but you were actually saying that it’s bad that a file is labeled a .txt file (for example)? Jesus dude.
I don’t get how people can’t be fired up about this! It’s just technically wrong to do this. Technically offensive, as I said and you don’t seem to get.
Why should people be mad about something that doesn’t affect anyone anywhere in any way?
Because you should be mad at things that are done wrongly. It’s okay to be, try it.
Now that’s just offensive.
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.
Then your argument makes even less sense than I thought. I thought you were making the at least somewhat reasonable argument that you should be able to use any character you wanted to name your files, but you were actually saying that it’s bad that a file is labeled a .txt file (for example)? Jesus dude.
I don’t get how people can’t be fired up about this! It’s just technically wrong to do this. Technically offensive, as I said and you don’t seem to get.
Why should people be mad about something that doesn’t affect anyone anywhere in any way?
Because you should be mad at things that are done wrongly. It’s okay to be, try it.
Sorry I have real things to do.
Keep Circulating the Tapes.
END OF LINE
(It hasn’t happened yet)
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.
Then your argument makes even less sense than I thought. I thought you were making the at least somewhat reasonable argument that you should be able to use any character you wanted to name your files, but you were actually saying that it’s bad that a file is labeled a .txt file (for example)? Jesus dude.
I don’t get how people can’t be fired up about this! It’s just technically wrong to do this. Technically offensive, as I said and you don’t seem to get.
Why should people be mad about something that doesn’t affect anyone anywhere in any way?
Because you should be mad at things that are done wrongly. It’s okay to be, try it.
Sorry I have real things to do.
Well then quit this forum then. OT.com is ostensibly about things that don’t really have any affect on the world.
But how would I make you have a aneurysm over MAC vs. Real PCs if I left?
Furthermore: I care about Star Wars (which has affected my life) and enjoy communicating with folks here about things, I really don’t care about file type extensions because it doesn’t affect my life in the slightest.
Keep Circulating the Tapes.
END OF LINE
(It hasn’t happened yet)
Imma just post Mack memes until this useless non-conversation dies down.
Non factual. Almost all of the most powerful applications that people use started or are only on the Mac, with some being on Windows and extremely rarely on Linux.
Not factual.
Nearly all of Adobe’s Creative Suite started on the Mac. Most of the main products of the Office suite (a Microsoft product, for that matter) started on the Mac. I can give more.
Imma just post Mack memes until this useless non-conversation dies down.
Non factual. Almost all of the most powerful applications that people use started or are only on the Mac, with some being on Windows and extremely rarely on Linux.
Not factual.
Nearly all of Adobe’s Creative Suite started on the Mac. Most of the main products of the Office suite (a Microsoft product, for that matter) started on the Mac. I can give more.
And yet they all run better on PC, weeeeird!
Keep Circulating the Tapes.
END OF LINE
(It hasn’t happened yet)
But how would I make you have a aneurysm over MAC vs. Real PCs if I left?
So you really want to have someone experience physical pain for your entertainment?
Imma just post Mack memes until this useless non-conversation dies down.
Non factual. Almost all of the most powerful applications that people use started or are only on the Mac, with some being on Windows and extremely rarely on Linux.
Not factual.
Nearly all of Adobe’s Creative Suite started on the Mac. Most of the main products of the Office suite (a Microsoft product, for that matter) started on the Mac. I can give more.
And yet they all run better on PC, weeeeird!
Imma just post Mack memes until this useless non-conversation dies down.
Non factual. Almost all of the most powerful applications that people use started or are only on the Mac, with some being on Windows and extremely rarely on Linux.
Not factual.
Nearly all of Adobe’s Creative Suite started on the Mac. Most of the main products of the Office suite (a Microsoft product, for that matter) started on the Mac. I can give more.
And yet they all run better on PC, weeeeird!
Prove it.
##### *NO.*****
Keep Circulating the Tapes.
END OF LINE
(It hasn’t happened yet)
Don’t do drugs, unless you’re with me.
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.
Then your argument makes even less sense than I thought. I thought you were making the at least somewhat reasonable argument that you should be able to use any character you wanted to name your files, but you were actually saying that it’s bad that a file is labeled a .txt file (for example)? Jesus dude.
I don’t get how people can’t be fired up about this! It’s just technically wrong to do this. Technically offensive, as I said and you don’t seem to get.
Why should people be mad about something that doesn’t affect anyone anywhere in any way?
Because you should be mad at things that are done wrongly. It’s okay to be, try it.
I’m mad at your posts…
I want this thread and the anime thread to have a beautiful baby abomination together.
I laughed at this. Hard. At work. People think I’m weird now. More-so than usual.
Stupid NRC induced double post.