3 ms·
This can only be a troll... 'all the open source image tools'? That seems like an intractable set to me. They shouldn't need to. I see there's an imlib2 webp
by yebyen 14y ago
This can only be a troll... 'all the open source image tools'? That seems like an intractable set to me. They shouldn't need to. I see there's an imlib2 webp loader. It is BSD licensed. I don't see that it came from Google.
So what's your point? We're supposed to be hating Facebook anyway, not Google in this article.
- DanBC 14y ago"Some of the most popular open source tools" would have been better. Google is a huge company, with many good programmers. A reference implementation is great. Provide patches to some of the most used open source products just helps Google spread their tech, and helps all those open source products. My post wasn't meant to be a dig at Google. Re-reading it I see that it could be read that way, and I apologise for that.
- yebyen 14y agoI understand. https://developers.google.com/speed/webp/download https://developers.google.com/speed/webp/download There is a set of command-line utilities, a library with source, and a codec for Windows Imaging Component which has no parallel in Linux that I am aware of. (save imlib2 and friends) I don't know any project that uses image formats in any way and does not link directly with libpng, libjpeg, lib(un)gif, or other directly supporting libraries that are tied to individual formats. There is an evas webp loader on eina, which is no help to Gnome or KDE users, and there are dozens if not hundreds of projects that probably need support to be added. Don't know how ubiquitous Windows Imaging Component is in MS-land, but it seems like a much easier problem to have solved.