TUAW Tip: The Importance of File Extensions

I like file extensions very much, and the way the mac handles them - when the setting is to show them. Here's why.

I want to name my docs the same thing when they are converted to or saved as different file format. This way, I know that all files with that name represent the same version of information. For example, I'll write my class syllabus in word format, and save a distribution version (for secretaries or to post on the web) as a pdf file. So: Bio101Fall05.doc and Bio101Fall05.pdf - this tells me they are the same version if I have to backtrack.

But Windows is a mess - horrible mess. I have to use Windoze to run a DNA analysis program, and when I bring a text file over saved with an extension, Windoze always puts the .txt extension on the file in addition to any other file name. Furthermore, when I want to save files of different formats in any windows program to the same file name (like .tiff and .jpeg for graphics) it doesn't let me! It will replace files with the same name, regardless of the different extension. So I get alot of messed up names: Image12EditJ and Image12EditT, with no extensions visible. Yes, you can alter whether extensions are visible or not in Windoze finder. However, many applications in Windoze cannot recognize formats of a file unless it has a freaking extension... go figure!

you raise some good points here. in an ideal world, exentsions wouldn't be necessary. unfortunately, as you imply, even users who use only macs and mac apps that don't rely on extensions need to use extensions so they can email files to their Windows-using friends/associates. So, even though they're not *technically* required 90+% of the time, we're all pretty much stuck with them -- whether we're new users who need to email a jpeg to a friend, or professionals who need to upload stuff to a website. Oh well. Thanks, Microsoft.

I used to hate file extensions, but I've decided that life is better with them. Besides, as a guy who makes a lot of web pages, it's absolutely essential to know what the extension on a given file is. Before the Web and before the days of trading files back and forth between different platforms, I really believed that it should be the other way around. Now, we need them.

I filed a feature request to Apple regarding this in 10.1 to change the user default to "Show all file extensions"

Obviously that request wasn't accepted well.

I'm still a fan of file extensions, even when they aren't explicitly needed.

Yes, file extensions have become one of those necessary evils in life. Unfortunately there aren't any better ways that have appeared for having file meta data which is obvious to the users. Both Windows and Unix have taken to using extensions, albeit that Unix hasn't limited itself to three characters.

I hope some day we can be rid of the system, but I don't see how until we eliminate the concept of proprietary document formats associated with applications.

The only flaw in this is that by default, Windows hides the extensions. So when user names a file on a Windows machine, they are still calling it what ever they want and not putting in or seeing the extension. However you are correct in that when a Apple file is moved over to Windows without and extension, Windows doesn't know what to do with it, but I am not sure that turning on show extensions is the best way to address the issue.

Jason, as the screenshot shows, just go to Preferences in Finder, click the Advanced tab (gear icon), and checkmark "Show all file extensions".

There's no "preferences mod"; he's just telling you what file is changed when you enable that option.

But you didn't say 1) a step by step on how to enable showing the file extensions and 2) what the heck you're talking about with the Finder preferences mod and how you change that file you listed.

Details?