jaredcheeda

7 ms·

1.
Node-FLIF Version 1.0.0 is released – FLIF image compression using Node.js/npm(github.com)
1 points by jaredcheeda 9y ago|0 comments
2.
by jaredcheeda 9y ago
Happy Koalaween! We just released a new version of Koa11y. It's an easy to use program to detect accessibility issues on webpages and output a report in different formats (HTML, JSON, CSV, Markdown, XML). It's designed to be usabl
3.
Koa11y – FOSS desktop app to detect accessibility (a11y) issues on webpages(open-indy.github.io)
3 points by jaredcheeda 9y ago|1 comments
4.
by jaredcheeda 9y ago
What about NW.js, It's the real hero here. They spent 5 years building up the platform, being used by thousands of companies and apps, basically inventing this technology; just to have GitHub buy up their intern and pay him to make a
5.
by jaredcheeda 10y ago
You won't ever fully replace GIF, at least not in the next decade. There are too many devices and apps/software that ONLY have GIF support due to the low computational footprint (designed for 1989 hardware). There's a reason
6.
by jaredcheeda 10y ago
The truncated version is basically a lower resolution. So if you have a 5000x5000px image and you display it on your page as 100x100px, it only needs to download a small amount of data to show it at that lower resolution. Obviously being a
7.
by jaredcheeda 10y ago
On September 19, 2016 Jon Sneyers wrote "I'm going to drop the "rc" and tag what we have now as v0.2. This will be FLIF16 and all bitstream-breaking changes will have to be in a new branch, which will become FLIF17 or FL
8.
by jaredcheeda 11y ago
For clarification, on the FLIF GitHub "Issues page", there is a ticket indicating an intention to build FLIF into FireFox's rendering engine Gecko, and also Servo (which will eventually replace Gecko). This ticket is a placeh
9.
by jaredcheeda 11y ago
The FLIF format isn't finished yet. There are optimizations still being made both in compression ratio and decoding performance. Encoding performance is a lower priority. Also it wouldn't really be a fair comparison to show this s
10.
by jaredcheeda 11y ago
Current plan is to keep lossless and lossy versions of the format in the same bitstream for encoders/decoders and to differentiate the output files encoded to be lossy as ".flyf" (Free LossY image Format), and those that are
11.
by jaredcheeda 11y ago
FLIF allows for animation, and it is very possible to interpret each frame of the animation as it's own layer. This would year the same lossless quality as a TIFF at a much smaller file size. Though FLIF isn't intended to be used
12.
by jaredcheeda 11y ago
Well TIFF has very poor compression leading to large file sizes compared even to PNG. And thus no one uses it on the web. FLIF has very good compression, it will only download the minimum amount of data required to display the image at it&#
13.
by jaredcheeda 11y ago
The first official version of FLIF has not been released yet, and currently they are discussing releasing it under Apache 2 or MPL (Mozilla Public License).
14.
by jaredcheeda 11y ago
The current decode time (on a lower end ARM CPU) is approx 1 megabyte per second. This of course will increase as the format is finalized and better/more optimized decoders are written for it. As well as with CPU speeds increasing. Tho
15.
by jaredcheeda 11y ago
The first official version of FLIF has not been released yet, and currently they are discussing releasing it under Apache 2 or MPL (Mozilla Public License).
16.
by jaredcheeda 11y ago
In the part where it says "Spot the difference" and everyone says "The BPG one looks worse". That's because BPG, even in "lossless" mode... is lossy. So you're taking a video with H.264 compression ar