I can imagine Safari and IE building support for this format entirely as a counter to Google’s WebP, since they already need support for HEVC as a matter of course.
Many current websites send very heavily compressed JPEG images to save bandwidth, and just live with the big hit to image quality. If they had a similar-filesize alternative that they could use for some or all clients that didn’t degrade image quality, and still was guaranteed to work smoothly, it’s plausible they might adopt it.
I don't think a format requiring JS to decode and negating the whole parallel download/decode thing has a chance regardless of the elegance.
It's not an imaging format discussion I this case.
As far as I can tell, this new format already has a better client compatibility story than JPEG 2000 right off the bat, as well as better quality for the same file sizes.
I believe part of the point of BPG is that it's an HEVC subset. If cameras can shoot HVEC, they have BGP hardware support.
Any new "image compression format" isn't going to gain widespread traction unless is can displace JPEG in terms of hardware support and ubiquity in cameras.
I was part of the JPEG-2000 support. The company I was with at the time had technology around how blocks were encoded (it gave up block independence at the benefit of 20+% encoding efficiency -- downside would be an intermediary step to reconstruct the JPEG steam).
None of those solutions took off.
Explain to me how beyond a hobbyist market BPG will make a splash?