Slashdot Mirror
GIF Support Returns to GD
g_adams27 writes "Legions of geeks and developers owe a debt of gratitude to Tom Boutell and his "gd" library, which powers the drawing and graphic-generating tools used by dozens of open-source projects. And now, with the expiration of the last Unisys patent on the GIF format, support for GIFs has finally been reinserted in gd. The GIF/PNG/MNG wars may continue, but having more options is good!"
I know I didn't.
I bet nobody in Unisys (at least nobody high up) even knew about this happening ... otherwise they would have realized they weren't making money in the last year and put it in the public domain and made a press release etc.
Shows you that a corporation like Unisys isn't dynamic. RSA on the other hand, was making money off their patent and decided that there's value in releasing it into the public domain prior to the patent expiration date.
The only thing gif does better than png is animation. Okay, on some rare occasions, gif compresses better. But most of the time, you have no reason to use gif instead of png.
Can you show me a mainstream, modern browser that doesn't understand both GIF and PNG?
The usual crowd of nincompoop Slashbots are going to crow "They should just leave it out! Everyone should use PNG anyway!!"
... GIF is still the only available option.
Let me answer that in advance by reminding everyone that GIF is a useful format. Everything can read it and display it. It's been around for two decades and is now a completely open and unencumbered standard.
And let's not forget that when you need to display an image that is non-lossy, and supports transparency, and displays properly in Internet Explorer (shame on you for using Internet Explorer in the first place, but we'll accept that a lot of people still do)
Tired of FB/Google censorship? Visit UNCENSORED!
I think the poster was trying to ask whether congresscritters can make a similar law and grant Unisys control again.
.. can the IP "rights" transfer back into Unisys hands at a later date if Congress so decides.
So the question is
It appears to me the answer is yes (thanks to cooperation of the supreme court).
It's YRO not because GIFs could violate your rights online, but because Unisys, the holder of a submarine patent on GIFs, could. That's one of the main reasons we switched to PNG. Now the patent expired, meaning our rights to use GIFs, without getting the pants sued off us, are back.
Please increase your clue level before posting. The article is correctly filed.
There's no sig like this sig anywhere near this sig, so this must be the sig.
I would suspect that camera developers chose JPG because it was a specification from the Joint Photographers Group (hence it's name). If you are going to sell something to photographers, you want to tie it to a standard that photographers are expected to approve of.
Note, I am not saying that it was the best standard to choose, simply that it made sense from a camera developer's standpoint.
I doubt seriously that GIF will be a standard for camra developers to select and store to.
I susect that for the forseable future, uncompressed images will be saved to TIFFs, and compressed (lossy) will be stored as JPG files. How long this status will stay, I can't predict, neither can I predict what standards will take over.
-Rusty
You never know...
Unless you know the business internals and license agreements of those companies, you have no idea whether they respected the patents or not. However, all major graphics program vendors (Adobe, JASC, etc.) have LICENSED the gif compression algorithm, and used it in their programs. Those who paid to use those programs have the right to create gifs.
These commercial softwares did not disrespect "IP-rights," they meticulously followed the law by doing exactly what's required to use the patented algorithm. They showed respect for the patent by paying to use the algorithm. Free software respected the same rights by not using what they hadn't paid to use (because they either couldn't or weren't willing to).
-Dan
Good point, but there's only so much the software can do. It would be nice if it at least defaulted to 8-bit if the image had few enough colors. I don't know whether apps typically do this or not. I usually use Paint Shop Pro, which allows you to choose between several output options -- I never use the defaults.
Software should provide options, but most users will simply accept the defaults, so a format like PNG that has many options creates a bit of a problem. Who do we blame, though? Is it the user for not knowing enough about the format they are using? The software for not being smart enough? The format creators for not making it simpler? Obviously I was blaming the users in the grandparent post, and you are correct to point out that this isn't completely fair.
For the record, the main problem is people using the wrong type of PNG -- 24 bit when 8 bit is the one that's actually comparable to GIF. It's unlikely that a PNG optimization program will help much in that case (though maybe some of them will change the PNG mode if it can be done losslessly -- but I haven't seen this).
PHP is definitely not the only user of GD. Heck, GD is a C library. There are a lot of C apps out there that use it.
Personally, I've only used GD via perl and the many perl libraries that use it, primarily GD.pm.
.-.--
*If* MS and Adobe were free software projects, Adobe would have gotten its simplified PNG library and had a product to market just as quickly. Another person could then have come along and at a later date and implemented the remaining filters. In this way Adobe gets a working product quickly, but at a later any missing features get filled in.
As it is the proprietory model delivered the fast product, but missed out on the 'incremental improvement' stage.