51–60 of 160 posts
This is on a fully-patched RHEL6 workstation: http://i.imgur.com/NleqJTD.png Another example of "use bleeding-edge tech or go fuck yourself" from the modern web.
This is not true: "A GIF is literally a sequence of independent images squeezed into the same file. An mp4 video can take advantage of all kinds of fancy compression techniques like keyframes and forward-predictive frames." That's not why the mp4 is smaller. A GIF is not [just] independent images, you can have each frame reuse pixels from previous frames. The mp4 is smaller because lossy jpeg compression is used on e…
Not quite true yourself :). GIFs store deltas, true, but they are still raster images. H.264 on the other hand contains specific techniques for compressing sequential frames, including things like recording only pixel motion for some frames. You can see it in those "corrupt movies" gifs (which on twitter would be mp4s... talk about irony) where you take a clip and remove some keyframes from it - then transformations…
This is not true: "A GIF is literally a sequence of independent images squeezed into the same file. An mp4 video can take advantage of all kinds of fancy compression techniques like keyframes and forward-predictive frames." That's not why the mp4 is smaller. A GIF is not [just] independent images, you can have each frame reuse pixels from previous frames. The mp4 is smaller because lossy jpeg compression is used on e…
Not quite true yourself :). GIFs store deltas, true, but they are still raster images. H.264 on the other hand contains specific techniques for compressing sequential frames, including things like recording only pixel motion for some frames. You can see it in those "corrupt movies" gifs (which on twitter would be mp4s... talk about irony) where you take a clip and remove some keyframes from it - then transformations…
The saddest part is that you can't add a zip to that gif and use twitter as a sharing platform. cat x.zip >> y.gif and upload would have been nice ;)
This is on a fully-patched RHEL6 workstation: http://i.imgur.com/NleqJTD.png Another example of "use bleeding-edge tech or go fuck yourself" from the modern web.
More like, "stop using technology from the late 80s or go fuck yourself". GIF is awful and nobody should reasonably expect sites to accommodate it anymore.
Earlier quoted context omitted.
What percentage of Twitter's users do you think use Linux for browsing? Much less RHEL. Anyway, this is purely a front-end enhancement mostly for the benefit of mobile users. Also lol @ mp4 being "bleeding edge" tech. It certainly is not. Even in the Linux community.
Changing the fundamental format of the content is a 'front-end enhancement' now? If it's for mobile users, why not present it just to mobile users? also lol @ your opinion about technology. even in the "linux community"
Anyway, that is why I asked the loaded question about how many users you think there are that browse Twitter.com on their RHEL box? Hint: HN is not a good sample to answer this.
And how is a ~14-year old technology (that has been ubiquitous now for at least 6 years) considered bleeding edge?
Earlier quoted context omitted.
More like, "stop using technology from the late 80s or go fuck yourself". GIF is awful and nobody should reasonably expect sites to accommodate it anymore.
Huh? HTML is older than GIF images. Should we stop accommodating that too?
This is on a fully-patched RHEL6 workstation: http://i.imgur.com/NleqJTD.png Another example of "use bleeding-edge tech or go fuck yourself" from the modern web.
Support for mp4 isn't bleeding-edge tech on other operating systems / distributions, unfortunately. It's a couple of years old in terms of being supported by Chrome; it's supported in Firefox as of last August. At this point, desktop configurations that can't play mp4s are at risk of being considered "broken."