Live data from Hacker News

Pik – a new lossy image format for the internet

github.com

21–30 of 151 posts

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

#22
post #19

Any patents on this?

It is licensed under Apache 2.0, so if Google has any patents on it they could not use them against users of this code or derivative code because of the terms of the license. This doesn't protect you from the several other irresolvable issues in software patents however.

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

#24
post #2

"This is not an official Google product." Can anyone explain this to me? It is posted under the Google organization. Are they just not actively supporting it?

In addition to what other replies stated, you can read Google's documentation on how open source projects (official and unofficial are released) here: https://opensource.google.com/docs/

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

#27
post #13
post #2

"This is not an official Google product." Can anyone explain this to me? It is posted under the Google organization. Are they just not actively supporting it?

It's written by a Google employee, and therefore Google owns all rights to it. However, in all other respects it's just an open source project written and supported in the authors' free time.

How could Google own something written and supported in the authors' free time?

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

#28
post #13

Earlier quoted context omitted.

It's written by a Google employee, and therefore Google owns all rights to it. However, in all other respects it's just an open source project written and supported in the authors' free time.

How could Google own something written and supported in the authors' free time?

Oppressive employment agreements

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

#30
post #26

Can anyone explain if there is something particularly new or interesting about this image format? Or do I have to read the source code?

Yes, you would have to read the source code. My guess reading the README.md is that due to the dependencies in the README.md its a JPEG competitor that is fast due to HEVC. The README.md even says this is still experimental. This project really looks too immature to be posted on HN without a technical breakdown. (This is not to disparage the software but for people to remain interested there would have to be at least some benchmark and it would be nice with a visual comparison).
Post reply on HN