Live data from Hacker News

Pik – a new lossy image format for the internet

github.com

101–110 of 151 posts

Re: Pik – a new lossy image format for the internet

#101
post #95

HEIF already exists as a standard [1] with comparable compression [2]. What does Pik hope to do better? (And please don't say "patent free" unless you are certain Pik will not infringe on those same patents) [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_For... [2] https://nokiatech.github.io/heif/technical.html

> And please don't say "patent free" unless you are certain Pik will not infringe on those same patents

HEVC/HEIF: Absolutely can't use because patents. Pik: Maybe can't use because patents.

Pik has potential to be useful, HEVC does not.

Re: Pik – a new lossy image format for the internet

#102
post #81

Earlier quoted context omitted.

Or maybe Google should avoid confusion and stop putting unofficial projects under github.com/google.

Pet projects done with googles time and resources can't easily be published elsewhere on github...

It might not have been done with Google's time and resources; Google likes to strong-arm employees into agreeing that Google owns their side projects. The `google` organization on GH is a compromise.

Re: Pik – a new lossy image format for the internet

#103
post #95

HEIF already exists as a standard [1] with comparable compression [2]. What does Pik hope to do better? (And please don't say "patent free" unless you are certain Pik will not infringe on those same patents) [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_For... [2] https://nokiatech.github.io/heif/technical.html

Maybe "The software currently requires an AVX2 and FMA capable CPU, e.g. Haswell." holds the secret? Some kind of experimental test bed for using CPU vector instructions to speed up compression/decompression? Disclaimer: I have no idea what I am talking about. For all I know possible use of these instructions is already a feature of HEIF and that statement is irrelevant.

Yep. Use of AVX2 and so forth a pretty standard thing to do to get decent performance for video/image encoding and decoding.

Worth noting: Skylake with Integrate Graphics includes an x265 encoder and decoder. If that can't be adapted to HEIF, that's a huge win for the format.

Re: Pik – a new lossy image format for the internet

#104
post #101
post #95

HEIF already exists as a standard [1] with comparable compression [2]. What does Pik hope to do better? (And please don't say "patent free" unless you are certain Pik will not infringe on those same patents) [1] https://en.wikipedia.org/wiki/High_Efficiency_Image_File_For... [2] https://nokiatech.github.io/heif/technical.html

> And please don't say "patent free" unless you are certain Pik will not infringe on those same patents HEVC/HEIF: Absolutely can't use because patents. Pik: Maybe can't use because patents. Pik has potential to be useful, HEVC does not.

Pik's documentation doesn't even have "patent free" as a goal.

Re: Pik – a new lossy image format for the internet

#105
post #96

Now if APNG would gather some steam, high quality animated fully alpha transparent images would be nice. Gif's 256 color and 1 level transparency is ok, but to do better work we need something like APNG, although not sure how well it compresses.

Pretty sure APNG is supported now in all browsers except Edge and IE. So not quite there yet, but we're getting close.

Re: Pik – a new lossy image format for the internet

#106
post #74
post #70

The title of this post is misleading. It's not an official Google product and is not called Google Pik. This is just a project named "Pik" that happens to be developed by Google employee(s).

Thanks, we've updated the submission headline.

thanks for the info and the edit :)

Re: Pik – a new lossy image format for the internet

#107

Earlier quoted context omitted.

That's not true, at least not in California. But if you made it with Google resources then yes they own it.

"That's not true, at least not in California." People, for the most part, very badly misunderstand what california law says. For most large diversified corporations, the corporation will own all of it, because it will "Relate at the time of conception or reduction to practice of the invention to the employer’s business, or actual or demonstrably anticipated research or development of the employer;" Note that it's com…

Since some folks have trouble reading between the lines: Google considers all code possibly relevant to its business interests, and treats employees (in)appropriately.

The only way to win is to not have ideas.

Re: Pik – a new lossy image format for the internet

#108
post #101

Earlier quoted context omitted.

> And please don't say "patent free" unless you are certain Pik will not infringe on those same patents HEVC/HEIF: Absolutely can't use because patents. Pik: Maybe can't use because patents. Pik has potential to be useful, HEVC does not.

Pik's documentation doesn't even have "patent free" as a goal .

This doesn't change that Pik's patent status is currently uncertain while HEVC's is known.

We can certainly discount Pik as soon as a patent that covers it is discovered, until then it's just a promising project to pay attention to.

Re: Pik – a new lossy image format for the internet

#109

Earlier quoted context omitted.

"That's not true, at least not in California." People, for the most part, very badly misunderstand what california law says. For most large diversified corporations, the corporation will own all of it, because it will "Relate at the time of conception or reduction to practice of the invention to the employer’s business, or actual or demonstrably anticipated research or development of the employer;" Note that it's com…

Since some folks have trouble reading between the lines: Google considers all code possibly relevant to its business interests, and treats employees (in)appropriately. The only way to win is to not have ideas.

Errr, what i wrote literally was not about Google, but a commentary on the state of the law.

You will find the same issue at any large diversified company. Quite literally.

Re: Pik – a new lossy image format for the internet

#110
post #68
post #36

Earlier quoted context omitted.

If you work at Google everything you make, even in your spare time, belongs to them. That's how the contracts work, unfortunately.

> If you work at Google __everything you make__, even in your spare time, belongs to them. Okay, google makes software and if you make software on your spare time maybe it's reasonable that company does not want to leak IP and thus produces these contracts. But what about these stupid examples: - Building a backyard deck for your house - Taking pictures as a hobby - Doing woodworking (e.g. making a chair and a table…

Building a baby?
Post reply on HN