Hacker News Reader

Legacy systems, web norms, and user habits dictate '.jpg' triumphs over '.jpeg' for compatibility, brevity, and conformity....Smack down...

My only friend and ally is the macOS standard Image Capture app which writes scanned files with the .jpeg extension.

I’m guessing this could even be a NeXT leftover because Image Capture is ancient. The .jpeg extension was more popular on 1990s Unix.

I think almost all Apple apps do this, e.g. Photos.app.

Which is super-annoying, even though I agree with in in theory. But generally the only reason I am writing an image to .jpg is to email it to somebody or upload it to some web app and that principled .jpeg filename extension certainly isn't helping compatibility..

.. and not .JFIF?

Originally extensions were only 3 characters long.

Originally as in Unix? I don’t think so.

But later on microcomputers in CP/M and thence MS-DOS, yes.

They didn't originate in Unix.