• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why do we still name files '.jpg' and '.mpg'?

N

notfred

Lifer
We gave up using '.htm' a long time ago in favor of '.html'. Why aren't we using '.mpeg' and .'jpeg' more often?
 
Originally posted by: isekii
Originally posted by: PrincessGuard
It requires 33.3% more work to type that extra letter.
Click to expand...

don't you mean 25% ?
Click to expand...

no, it's 33%.

But I dont think the extra work to type the letter is the reason.


Why was there two to begin with? windows 3.1 only supported files with 3 character extensions.
 
Originally posted by: edmicman
why not use .picture or .photograph_of_my_dog or .movie ??
Click to expand...

Because "picture" and "photograph_of_my_dog" are not standard file types. JPEG and MPEG are. Do you even know why filenames have extensions?
 
My gut instinct is that html was developed in Unix where they didn't have to have 3-letter extensions, while mpeg and jpeg were developed in Windows by people who were brainwashed by the 3-letter extension industry.
I do see jpeg and mpeg here and there.
 
Originally posted by: notfred
Originally posted by: isekii
Originally posted by: PrincessGuard
It requires 33.3% more work to type that extra letter.
Click to expand...

don't you mean 25% ?
Click to expand...

no, it's 33%.

But I dont think the extra work to type the letter is the reason.


Why was there two to begin with? windows 3.1 only supported files with 3 character extensions.
Click to expand...


25% less work typing .jpg over .jpeg and 33.3% more work typing .jpeg over .jpg
 
3-letter extensions identified the type of file to the OS in DOS, which I believe stole it from CP/M. The OS needed to know that .BAT for example should be fed to the batch-file interpreter while .EXE should be fed to the program loader.

So much existing code still assumes 3-letter extensions that using .jpeg for example would keep that code from opening the file properly, or even keep the file from showing up in "open file" dialog boxes that filter out files by their extension.
 
Originally posted by: DaveSimmons
3-letter extensions identified the type of file to the OS in DOS, which I believe stole it from CP/M. The OS needed to know that .BAT for example should be fed to the batch-file interpreter while .EXE should be fed to the program loader.

So much existing code still assumes 3-letter extensions that using .jpeg for example would keep that code from opening the file properly, or even keep the file from showing up in "open file" dialog boxes that filter out files by their extension.
Click to expand...

Name an application that will recognize a file named '.jpg' but not one named '.jpeg'.
 
Originally posted by: Fiveohhh
Originally posted by: notfred
Originally posted by: isekii
Originally posted by: PrincessGuard
It requires 33.3% more work to type that extra letter.
Click to expand...

don't you mean 25% ?
Click to expand...

no, it's 33%.

But I dont think the extra work to type the letter is the reason.


Why was there two to begin with? windows 3.1 only supported files with 3 character extensions.
Click to expand...


25% less work typing .jpg over .jpeg and 33.3% more work typing .jpeg over .jpg
Click to expand...

In the context it is 33.3%, no one should have mentioned 25%
 
Originally posted by: notfred
Originally posted by: edmicman
why not use .picture or .photograph_of_my_dog or .movie ??
Click to expand...

Because "picture" and "photograph_of_my_dog" are not standard file types. JPEG and MPEG are. Do you even know why filenames have extensions?
Click to expand...

I think he was being sarcastic, right?
 
Originally posted by: notfred
Originally posted by: DaveSimmons
3-letter extensions identified the type of file to the OS in DOS, which I believe stole it from CP/M. The OS needed to know that .BAT for example should be fed to the batch-file interpreter while .EXE should be fed to the program loader.

So much existing code still assumes 3-letter extensions that using .jpeg for example would keep that code from opening the file properly, or even keep the file from showing up in "open file" dialog boxes that filter out files by their extension.
Click to expand...

Name an application that will recognize a file named '.jpg' but not one named '.jpeg'.
Click to expand...
I just wrote one in VB. It crashes your system if you use jpeg. It first randomly deletes files.
 
Originally posted by: Skoorb
Originally posted by: notfred
Originally posted by: DaveSimmons
3-letter extensions identified the type of file to the OS in DOS, which I believe stole it from CP/M. The OS needed to know that .BAT for example should be fed to the batch-file interpreter while .EXE should be fed to the program loader.

So much existing code still assumes 3-letter extensions that using .jpeg for example would keep that code from opening the file properly, or even keep the file from showing up in "open file" dialog boxes that filter out files by their extension.
Click to expand...

Name an application that will recognize a file named '.jpg' but not one named '.jpeg'.
Click to expand...
I just wrote one in VB. It crashes your system if you use jpeg. It first randomly deletes files.
Click to expand...

After e-mailing your wife all the notes you've sent to your mistress, right? 😛
 
Originally posted by: Lithium381
maybe i'm just old fasioned, but when i can, i adhere to the 8.3 filename structure
Click to expand...

Why? you really prefer a file named "tspbwbwi.mp3" to "The Smashing Pumpkins - Bullet with Butterfly Wings.mp3"?
 
Originally posted by: notfred
Originally posted by: DaveSimmons
3-letter extensions identified the type of file to the OS in DOS, which I believe stole it from CP/M. The OS needed to know that .BAT for example should be fed to the batch-file interpreter while .EXE should be fed to the program loader.

So much existing code still assumes 3-letter extensions that using .jpeg for example would keep that code from opening the file properly, or even keep the file from showing up in "open file" dialog boxes that filter out files by their extension.
Click to expand...

Name an application that will recognize a file named '.jpg' but not one named '.jpeg'.
Click to expand...

None of my gfx applications know anything of file extensions; rather, they are concerned with the headers only. So in that case, I'd say all applications. I could feed it a gif with a jpeg header and it would still treat it as a jpeg.
 
Originally posted by: Descartes
Originally posted by: notfred
Originally posted by: DaveSimmons
3-letter extensions identified the type of file to the OS in DOS, which I believe stole it from CP/M. The OS needed to know that .BAT for example should be fed to the batch-file interpreter while .EXE should be fed to the program loader.

So much existing code still assumes 3-letter extensions that using .jpeg for example would keep that code from opening the file properly, or even keep the file from showing up in "open file" dialog boxes that filter out files by their extension.
Click to expand...

Name an application that will recognize a file named '.jpg' but not one named '.jpeg'.
Click to expand...

None of my gfx applications know anything of file extensions; rather, they are concerned with the headers only. So in that case, I'd say all applications. I could feed it a gif with a jpeg header and it would still treat it as a jpeg.
Click to expand...

So then it recognizes both .jpeg and .jpg named files, and therefore doesn't fit my criteria.
 
Originally posted by: notfred
Originally posted by: Lithium381
maybe i'm just old fasioned, but when i can, i adhere to the 8.3 filename structure
Click to expand...

Why? you really prefer a file named "tspbwbwi.mp3" to "The Smashing Pumpkins - Bullet with Butterfly Wings.mp3"?
Click to expand...

I think lucid descriptions are best placed in file headers (ID3 for MP3s, PE for EXEs, whatever), not in the name itself. A name should be a mnemonic, and nothing more. That being said, I still use somewhat lengthy filenames, but I never put spaces in them; I still use the CLI about 50% of the time.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top