Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google unkills JPEG XL?

tonisagrista.com

Post reply on HN
Print view View original

31–40 of 283 posts

Re: Google unkills JPEG XL?

#31

Post by majora2007 »

PaulHoule wrote: post #8
Finnucane wrote: post #2

Cool, that means it'll appear in ebook reading systems in five to ten years.

It'll be in PDF sooner, and my experience is that PDF >> any other system for ebooks. I liked the idea of EPUB but when I recently installed an EPUB reader to read some files I was shocked at how awful it looked whereas for 15 years I've been reading PDF files on tablets with relish.

That's interesting, I absolutely hate PDF. Lack of metadata for collecting, format is difficult to support, doesn't layout well on mobile, and very limited customization (like dark mode, changing text size, etc).

Only benefit is browsers have built-in support for the format.

Re: Google unkills JPEG XL?

#32

Post by jeffbee »

ocdtrekkie wrote: post #3

As a monopoly, Google should be barred from having standards positions and be legally required to build and support the web standards as determined by other parties. The insanity that the web platform is just "whatever Google's whims are" remains insane and mercurial. The web platform should not be as inconsistent as Google's own product strategies, wonder if XSLT will get unkilled in a few months.

Nobody is stopping you from using jpegxl.

Re: Google unkills JPEG XL?

#33

Post by ocdtrekkie »

dpark wrote: post #27
ocdtrekkie wrote: post #20

Earlier quoted context omitted.

There are other key browser implementers. Google should not have more than an advisory role in any standards organization.

The other key browser implementers are also part of WHATWG. Who do you suppose should be in charge of web standards? I can’t imagine the train wreck of incompetence if standards were driven by bureaucrats instead of stakeholders.

And those implementers should make decisions, Google should be bound by the FTC to supporting their recommendations.

Honestly, what's really funny here is how absolutely horrified people are by the suggestion a single company which has a monopoly shouldn't also define the web platform. I really think anyone who has any sort of confusion about what I commented here to take a long, hard look at their worldview.

Re: Google unkills JPEG XL?

#34

Post by majora2007 »

excusable wrote: post #24
ryanmcbride wrote: post #7

Earlier quoted context omitted.

honestly hate webp so happy about this

I don't know much about webp. Just have checked the wiki, it looks nice. So for which reason you hate it?

I don't know much about webp other than you get about 50% savings in compression vs png/jpeg, but it does have some hard limits on sizes of images. It doesn't do well with webtoon reading formats (long strip format).

Otherwise, I love webp and use it for all my comics/manga.

Re: Google unkills JPEG XL?

#35

Post by leosanchez »

majora2007 wrote: post #31
PaulHoule wrote: post #8

Earlier quoted context omitted.

It'll be in PDF sooner, and my experience is that PDF >> any other system for ebooks. I liked the idea of EPUB but when I recently installed an EPUB reader to read some files I was shocked at how awful it looked whereas for 15 years I've been reading PDF files on tablets with relish.

That's interesting, I absolutely hate PDF. Lack of metadata for collecting, format is difficult to support, doesn't layout well on mobile, and very limited customization (like dark mode, changing text size, etc). Only benefit is browsers have built-in support for the format.

One thing I like about PDF is the annotations (notes & highlights) are embedded in the PDF itself. That is not the case for EPUB files, each EPUB reader stores annotations in its own proprietary format.

Re: Google unkills JPEG XL?

#37

Post by EMM_386 »

Isn't this due to the 100M+ line C++ multi-threaded dependency being a potential nightmare when you are dealing with images in browsers/emails/etc. as an attack surface?

I think both Mozilla and Google are OK with this - if it is written in Rust in order to avoid that situation.

I know the linked post mentions this but isn't that the crux of the whole thing? The standard itself is clearly an improvement over what we've had since forever.

Re: Google unkills JPEG XL?

#39

Post by xg15 »

simonw wrote: post #16
ocdtrekkie wrote: post #3

As a monopoly, Google should be barred from having standards positions and be legally required to build and support the web standards as determined by other parties. The insanity that the web platform is just "whatever Google's whims are" remains insane and mercurial. The web platform should not be as inconsistent as Google's own product strategies, wonder if XSLT will get unkilled in a few months.

Having key browser implementers not involved in the standards processes is what lead us to the W3C wasting several years chasing XHTML 2.0.

There is a difference between having them "involved" and them being the only authority in the entire process.
Post reply on HN