Hacker Newsnew | past | comments | ask | show | jobs | submit | Caspy7's commentslogin

Google Research was central in developing and continuing to push JPEG XL.

The Google Chrome folks are the ones who decided to disallow it. You could argue that they are trying to kill it, but certainly not Google at large.


Lots of people are using AV1. They just don't know it.


I believe MacOS has full support. Windows now has support available as a free installable plugin.

Mozilla said that the current decoder state was unacceptable but if Google Research wrote them a Rust version that met their shippable criteria they'd ship it. That's planned to be done this summer. So I'm optimistic Firefox will ship support (courtesy of Google Research) within the year.

That would just leave Chrome support and Windows to ship by default. I'm hoping Firefox's support would cause pressure on the Chrome team.


Goodly amount of static here - unclear to me how much of it is added and how much is original.

https://www.my80stv.com/


Ok, so this is one step in such hyper-fast data transmission. What would be the other hurdles?


*she


They also have a much longer history than Chrome.

Kinda glad they disallowed the extensions that had near unfettered access to browser internals.


None that I'm aware of but Firefox has committed to maintaining the more powerful MV2 content blocking APIs that Google is removing.


Brave has committed to MV2 but they will need their own store first because the chrome web store is kicking out MV2 extensions. So far, they don’t have their own store.


They have explicitly not committed: https://twitter.com/BrendanEich/status/1534905779630661633

> We could fork them back in at higher maintenance cost. No point in speculating — I don’t write checks of unknown amount and sign them, and Google looks likely to keep V2 support for a year (thanks be to “enterprise”).


https://twitter.com/BrendanEich/status/1534893414579249152

> Brave will support uBO and uMatrix so long as Google doesn’t remove underlying V2 code paths (which seem to be needed for Chrome for enterprise support, so should stay in the Chromium open source). Will Google Chrome Web Store really kick them out over V2? We will host if needed.

https://twitter.com/BrendanEich/status/1534905779630661633

> > I’d be interested to hear a plan for Brave on what will happen if upstream removes the code paths needed for pre-v3 ad blockers.

> We could fork them back in at higher maintenance cost. No point in speculating — I don’t write checks of unknown amount and sign them, and Google looks likely to keep V2 support for a year (thanks be to “enterprise”).


I see my misunderstanding, they're specifically maintaining the webRequest interface


> I see my misunderstanding, they're specifically maintaining the webRequest interface

They aren't specifically maintaining anything. Brave's CEO doesn't "write checks of unknown amount[s] and sign them".


I think you're thinking of Firefox.


In my experience, most of the time black drawing like that is associated with GPU driver issues.


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: