News for hackers. Stuff that matters.
Re:Hey Ho, GIFs Must Go (1999) by mysterydip on Saturday October 26, 2019 @11:58AM (#21364420)
Was the original focus on size or performance for animated GIFs? The more you compress something, generally the more processing is required to restore it. I started using the web in the mid 90s, and animated GIFs were everywhere.
Re:Hey Ho, GIFs Must Go (1999) by nemo on Saturday October 26, 2019 @12:22PM (#21364558)
Pretty sure the original focus was just getting something that worked to display an animation. Animated gifs are an archaic, inefficient video format. Each frame of video is included in the file. You can optimize with a global color table and a few tricks to help cut size but they're incredibly inefficient compared to modern alternatives. Bigger sites like Twitter/Facebook convert gifs to .mp4s and serve .mp4 where possible since it saves a lot of bandwidth.
Re:Hey Ho, GIFs Must Go (1999) by ISL on Saturday October 26, 2019 @12:35PM (#21364644)
I suspect the key to the explosion of animated gifs was that everything supported gif and that it was largely incapable of nefarious/annoying activity (unlike flash).
Re:Hey Ho, GIFs Must Go (1999) by dredmorbius on Saturday October 26, 2019 @02:23PM (#21365315)
There's a fair bit of annoyance possible with GIFs, a fact I exploited when Google+ decided to:

1. Allow animations in the "Hero" user profile image.

2. Make that image permanently fixed to the top of the screen on the profile page.

3. As users increased window size to see more text and less hero, the image would scale to as much as 3/4 of the screen.

4. The hero was included on the "hover card" for users and would show up in all kinds of locations throughout the service. I still have that collection....

I spent an hour or so researching "annoying gifs", and settled on a rapid red-green-blue stroboscopic rotation. I don't know the cycle time, but it was probably a few times per second.

Google eventually relented. Well, they eventually shitcanned the whole site, but that's another story.

Trying to find animated images that weren't mind-bendingly annoying to me is how I ended up with the "space alien cat" image and avatar. The original had a rotating set of astronomical images in the glasses, I eventually applied the Crab Nebula as a static fill (tried the Cat's Eye, but ironically, it didn't work particularly well). That's the hero I use at several sites (Ello, Mastodon), and is the inspiration to the avatar I use as well.

Later at another site at which gratuitous annoying gif use was prevalent, I found a few static-but-apparently-moving optical illusion images, again to make the point that annoying images are annoying. The point was somehow missed by that crowd. That site also died.

TL;DR: animated gifs and even static images can be plenty annoying.

Re:Hey Ho, GIFs Must Go (1999) by jacquesm on Saturday October 26, 2019 @12:48PM (#21364720)
> Each frame of video is included in the file.

There is a trick where subsequent frames use transparency for non-changed parts of the image which gives a much better compression ratio than you might think.

Re:Hey Ho, GIFs Must Go (1999) by leeoniya on Saturday October 26, 2019 @01:48PM (#21365124)
this works well if you have a static background and a moving sprite. no so much if your background moves (or video).
Re:Hey Ho, GIFs Must Go (1999) by PavlovsCat on Saturday October 26, 2019 @01:55PM (#21365159)
The animated gifs that were everwhere generally were pixel animations rather than video.
Re:Hey Ho, GIFs Must Go (1999) by leeoniya on Saturday October 26, 2019 @01:59PM (#21365173)
well sure, when we had little bandwidth to even download a photo.
Re:Hey Ho, GIFs Must Go (1999) by PavlovsCat on Saturday October 26, 2019 @02:09PM (#21365245)
Not all animated pixel art was for lack of video, just like not all ascii art was and is for lack of images. Recording a video is a wholly different process to animating a 16x16 smiley. If anything, at least by now, I think more people record video because they can't draw, than people draw because they can't afford the equipment or bandwith for video.
Re:Hey Ho, GIFs Must Go (1999) by userbinator on Saturday October 26, 2019 @07:29PM (#21366971)
use transparency for non-changed parts of the image

In other words, similar to what video codecs do with "skipped macroblocks", except at a far more granular level. One wonders how efficient it would be if GIF was extended with things like motion vectors... but between the transparency/delta-enocding and the multi-palette "layering", you can sort of see the beginnings of a video codec.

Re:Hey Ho, GIFs Must Go (1999) by bbanyc on Saturday October 26, 2019 @06:26PM (#21366636)
There's also the trick where you can redefine the palette for each consecutive frame, and set the "delay" between frames to zero, in order to get more than 256 colors in a single image.

This is so horrendously inefficient it should be a crime. But it's still a GIF, and anything that can display animated GIFs can display it too.

Re:Hey Ho, GIFs Must Go (1999) by Dylan16807 on Sunday October 27, 2019 @02:05AM (#21368106)
Not that that means it will display entirely correctly. Browsers generally treat delays of 0 or 1 centiseconds as errors, and instead sit on that frame for a tenth of a second.
Re:Hey Ho, GIFs Must Go (1999) by Enginerrrd on Saturday October 26, 2019 @12:14PM (#21364519)
At the data rates we had available in the 90's, size was performance over the internet.

I am absolutely incredulous that people choose to use a GIF over a proper video format to share video on places like Reddit in this day and age. I don't understand the motivation to do so.

Re:Hey Ho, GIFs Must Go (1999) by hombre_fatal on Saturday October 26, 2019 @12:52PM (#21364741)
Well, these days imgur/gfycat will encode your gif as a video. Not sure I even see gifs much anymore.

Also, where have you been able to casually upload video to share quick bites like a cat making a funny face? You aren't going to upload a 12 second silent video to youtube. Up until very recently, gifs were the only permissible way to share this sort of content.

Re:Hey Ho, GIFs Must Go (1999) by pjc50 on Saturday October 26, 2019 @03:47PM (#21365771)
The huge advantage of gif was that it went in the <IMG> element. It behaves like a picture that moves, and can be uploaded to picture hosting services.

Video, until maybe the last 5 years, didn't.

Re:Hey Ho, GIFs Must Go (1999) by gsich on Saturday October 26, 2019 @07:58PM (#21367085)
It still doesn't. No loop control. Yeah you have HTML tags and whatnot, but the loop info must be inside the video itself, not as external metadata.
Re:Hey Ho, GIFs Must Go (1999) by edflsafoiewq on Saturday October 26, 2019 @09:04PM (#21367301)
Github is still full of GIFs for exactly this reason.
Re:Hey Ho, GIFs Must Go (1999) by cm2012 on Saturday October 26, 2019 @01:48PM (#21365122)
Because gifs can't have volume. I don't want my phone to make noises when I'm browsing the web.
Re:Hey Ho, GIFs Must Go (1999) by bredren on Saturday October 26, 2019 @01:52PM (#21365143)
There is also still generally more broadly supported preview rendering of gif vs newer formats.

Also probably more addressable / available tools for anim gif creation.

Re:Hey Ho, GIFs Must Go (1999) by caro_douglos on Saturday October 26, 2019 @02:43PM (#21365432)
Signal messenger doesn’t support webp across devices (last time I checked)....so I use jiffy format
Re:Hey Ho, GIFs Must Go (1999) by harshreality on Saturday October 26, 2019 @04:44PM (#21366059)
Then your browser should have an option to mute-embedded-video-by-default. Problem solved.

Don't blame a web video format/standard for UI failures.

Re:Hey Ho, GIFs Must Go (1999) by coribuci on Saturday October 26, 2019 @06:15PM (#21366591)
> Then your browser should have an option to mute-embedded-video-by-default. Problem solved.

I think you don't understand the modern web. If something is crappy the user shall have it. JS was always considered crappy but now is the best new thing. And you also missed tbe latest web/UI/UX development. From the web designer point of view the user is an idiot which must be punished for every attempt to customize something.

> Don't blame a web video format/standard for UI failures.

They are not UI failures. They are done on purpose.

Re:Hey Ho, GIFs Must Go (1999) by phkahler on Saturday October 26, 2019 @12:37PM (#21364658)
Because it's a "gif" not a WebP. If you want a format to catch on, the language needs to roll off the tongue. Even though I hate the word "podcast" and it sounds apple specific even though it's not, it sound a lot better than WebP.
Re:Hey Ho, GIFs Must Go (1999) by geofft on Saturday October 26, 2019 @01:48PM (#21365125)
"Do I look like I know what a JPEG is? I just want a picture of a got-dang hot dog."

https://youtu.be/QEzhxP-pdos

Re:Hey Ho, GIFs Must Go (1999) by buckminster on Saturday October 26, 2019 @01:06PM (#21364836)
I got the impression from the spec that it was originally designed to support retaining the compression dictionary across frames, which would have produced much smaller files at no cost to the decoder. But this wasn't explicit, it didn't get implemented, and the second spec ruled it out.

It could have very easily been better. I'm not sure what the moral is.