An Honor for the Creator of the GIF
bits.blogs.nytimes.com
bits.blogs.nytimes.com
Which has, conservatively, been around forever
>I worked with the creator of GIF (Steve Wilhite) when I was still employed by CompuServe. Steve always pronounced it "jiff" and would correct those who pronounced it with a hard G. "Choosy developers choose GIF" (spinning off of a historically popular peanut butter commercial).
The reason people use a hard G is because that's what makes sense given the wording of the acronym. Unless I've been pronouncing "graphics" wrong this whole time?
Slowly is a bit of an understatement. The format has been in widespread use for a quarter century.
PNG can't be used to make animations. GIF can. That alone is enough to ensure GIF will be around for a long, long time.
If you've been on the Internet over 15 years then this will not be news to you. The other thing I find interesting about the GIF format is how everyone assumes it was designed for animation. I saw someone on reddit "knowingly" tell another redditor "oh yeah there can be non animated GIFs they just consist of a single frame of animation."
Back during the dotcom boom, there was a joke: "We'll hire anyone who can spell GIF." At some point even the joke transitioned to a hard G sound. Some of us long ago decided to 'go with the flow'.
[1] This was due to a freeware program called JPEGView, which was often set up as the default viewer for .JPG files. http://en.wikipedia.org/wiki/JPEG_File_Interchange_Format
No one has been able to get their act together and propose a successful PNG animation format, but I'm disappointed that the "PNG in GIF" proposal never took off. Size wouldn't be so bad since most images would share a global color space, and browser makers could easily implement it.
ftp://ftp.simplesystems.org/pub/png-group/documents/history/png-in-gif-proposal-20070413.txt
You already mentioned the specification ( http://www.w3.org/Graphics/GIF/spec-gif89a.txt ). Did you use anything else?
Extensibility is provided for in the specification, but the actual implementation within each application extension is, of course, application-specific.
The extensions I know about:
- NETSCAPE (animation)
- NETSCAPE (buffering)
- ANIMEXTS (same as Netscape animation)
- GIFCONnb (found this GIF Construction Set extension during testing but didn't try to reverse engineer it)
The only one of consequence is the animation one.
The page I used at the time to describe the animation extension no longer exists, but this page describes it and others:
/me ducks
Gib, short for giblet, the innards of a bird, can be (and is) pronounced both ways — "j"iblet and "g"iblet. Where I'm from, it's always been "j"iblet, but I wouldn't mind if someone pronounced it differently.
http://translate.google.com/#en/en/GIF%20or%20JIF...%0Agif%2....
Google's Text-to-Speech seems to pronounce it with a Soft G.
here's what we've got at nuance: GIF or JIF -> http://bit.ly/1938drD.
the google translate tts models are older than their android models (particularly network tts), and it seem as though it still treats it similarly -> http://bit.ly/12tpCol
See http://en.wikipedia.org/wiki/Amerigo_Vespucci , http://en.wikipedia.org/wiki/Martin_Waldseem%C3%BCller , and http://en.wikipedia.org/wiki/Naming_of_America#Etymology_and...