uncompressed

It is 22GB compressed (250GB uncompressed) while Wikidata is 5GB compressed (49GB uncompressed) [1].

Running 'Hello World' from an uncompressed class file takes 0.12s, and most software is quite a bit larger than a couple lines of bytecode in an single uncompressed class file.

Later this year it will begin downlinking the full set of uncompressed, full-resolution images, including those in color.

Also when they release the pic on Twitter in crappy form before they release it in uncompressed form.

Can you tell the difference between uncompressed vs 320 kbps vs 128 kbps in a blind test?

On my desktop, the english dictionary is ~1 megabyte uncompressed, and compresses to ~250k with gzip.

Recently, there was a page on HN with an uncompressed 12 MB banner photo.

It would be silly to send uncompressed HD video to the Apple TV when lossless or nearly lossless compression could be used.

So relative to uncompressed file size, React will be compressed more than say Backbone.

The uncompressed images from the fly-by will take the roughly 16 months you mentioned, but there will be smaller, compressed images before that.

Later that day, on my own computer, I ran the uncompressed and compressed files through a bit-by-bit comparison program.

And 30mbit upload isn't enough to stream uncompressed video in 1080p.

No, because it's inefficient as hell (I wasn't joking when I said "less efficient than uncompressed bitmaps", it really is), and not all viewers support it.

Uncompressed, our test data was at 4GB, but went down to about 400MB after HBase compressed it.