News for hackers. Stuff that matters.
Re:Google Is Already Experimenting with WebP2 as Successor t... by TonyTrapp on Monday November 16, 2020 @08:16AM (#25111228)
Maybe we can slow down development a little bit and actually design a format that will last for another 30 years instead of requiring browsers to support yet another hot new format every five years.
Re:Google Is Already Experimenting with WebP2 as Successor t... by mpol on Monday November 16, 2020 @08:35AM (#25111413)
This is one of the many problems that come from Google having so much market power. This is really the Google development practices being forced onto everyone; iterate fast, create new stuff and throw old stuff away when you feel like it.

I do hope other browser makers like Mozilla Firefox and Apple Safari will hold back on this, like they should have done with Webp v1.

Re:Google Is Already Experimenting with WebP2 as Successor t... by jefftk on Monday November 16, 2020 @09:03AM (#25111711)
WebP was introduced in September 2010, Mozilla started supporting it in Firefox in 2019, and Apple is just adding it to Safari now. You think they should have waited longer than 10 years?

(Disclosure: I work for Google, speaking only for myself)

Re:Google Is Already Experimenting with WebP2 as Successor t... by mpol on Monday November 16, 2020 @11:37AM (#25113684)
Yes, I also think they should have waited indefinitely. I don't trust Google to care about backwards compatibility and keep on supporting Webp v1 forever, I would expect them to drop it before even dropping jpeg or png. Especially in this case, where it mostly serves Google and other big web corporations, and not regular users.

Mozilla always had the stance that they wouldn't just add support for technology that might be just a passer-by technology. I think that was the right choice and I think it is a shame they added support for webp recently.

I can even imagine this to be market practice, where they add new stuff, where Apple and Mozilla and newcomers have to chase Google's fad of the day, while Google has enormous resources for Chrome. You can call me paranoid, I probably am :)

Anyway, if Google Chrome ditches Webp v1 in the next 10 years, I will not be that guy to say "Told you so!", but I will think it for sure.

Re:Google Is Already Experimenting with WebP2 as Successor t... by layoutIfNeeded on Monday November 16, 2020 @12:53PM (#25114763)
Nah, why would Google do that? Oh wait... that’s exactly what they’re doing with HTTP/2 Push.
Re:Google Is Already Experimenting with WebP2 as Successor t... by jefftk on Monday November 16, 2020 @12:58PM (#25114822)
Server push is an optional extra, and the browser can drop support without hurting compatibility at all.

The browser cannot drop support for an image format without major compatibility issues.

If you would like to bet on whether webp is still supported in Chrome in a decade I'd be happy to ;)

(Disclosure: I work for Google, and have no internal information on this)

Re:Google Is Already Experimenting with WebP2 as Successor t... by lukeramsden on Monday November 16, 2020 @09:54AM (#25112340)
They should have waited indefinitely. WebP has been a big source of confusion for non-technical people I know, trying to download images from the internet.
Re:Google Is Already Experimenting with WebP2 as Successor t... by xbmcuser on Monday November 16, 2020 @10:15AM (#25112652)
If you want to stop progress for the least technically inclined to accept you will stop all progress for ever.
Re:Google Is Already Experimenting with WebP2 as Successor t... by lukeramsden on Monday November 16, 2020 @10:46AM (#25113069)
> If you want to stop progress for the least technically inclined to accept you will stop all progress for ever.

This is a strawman, at no point am I or would I ever claim this is a good idea.

At what point is progress too much progress? Why can't we also balance these things with backwards compatibility, interoperability, accessibility, and other such things?

> least technically inclined

How many people actually know what WebP is, as opposed to thinking its some sort of bug with google or their browser? The least technically minded are more than a majority of users, more like the vast majority. Is their usage not valued?

Re:Google Is Already Experimenting with WebP2 as Successor t... by seba_dos1 on Tuesday November 17, 2020 @11:35AM (#25125719)
Once WebP starts to get used more and more and people will stumble on issues with *.webp files they have no idea what to do with, their OSes and tools that they use will start to handle WebP files and the users will eventually learn what it is the same way they learned what JPEG is in the past. I don't know where the line of "too much progress" is, but you need to start that feedback loop somewhere.
Re:Google Is Already Experimenting with WebP2 as Successor t... by srgpqt on Monday November 16, 2020 @08:44AM (#25111496)
Safari only just got webp support super recently. Seems like they held back on it long enough...
Re:Google Is Already Experimenting with WebP2 as Successor t... by Eric_WVGG on Monday November 16, 2020 @09:55AM (#25112354)
Also note that it’s only Safari 14 on the new OS releases; Safari 14 on Mojave can’t view them.
Re:Google Is Already Experimenting with WebP2 as Successor t... by blihp on Monday November 16, 2020 @08:58AM (#25111650)
Not going to happen as long as people keep following their lead. It's in Google's interest to do things like maximize compression (especially for video and images) since it reduces their operational costs in the form of transmitting fewer bytes. Sure it benefits everyone (a bit), but while others might prioritize a bit more stability in standards, Google (and other major hosting services) value the reduced opex now. For most of the rest of us, we're well into diminishing returns on chasing the latest codec.
Re:Google Is Already Experimenting with WebP2 as Successor t... by SahAssar on Monday November 16, 2020 @10:08AM (#25112544)
Do you think that image (or video since a lot of tech overlaps) formats move so slowly that over 30 years there is no innovation worth considering?
Re:Google Is Already Experimenting with WebP2 as Successor t... by otabdeveloper4 on Monday November 16, 2020 @10:39AM (#25112979)
I'm pretty sure feature churn and foisting technical debt onto your competitors is a feature, not a bug for Google.
Re:Google Is Already Experimenting with WebP2 as Successor t... by liveoneggs on Monday November 16, 2020 @08:20AM (#25111288)
why bother when you can beta test on the most popular piece of software in continuous use around the world?
Re:Google Is Already Experimenting with WebP2 as Successor t... by Spivak on Monday November 16, 2020 @09:36AM (#25112102)
Because nobody actually needs to use this format if it doesn't benefit them. If the headline was "Google developing new proprietary image format to reduce web traffic to Google services by by 2% in Chrome" it would be a non-issue.

It seems odd that Google is being punished for releasing their work to anyone who wants it.

Re:Google Is Already Experimenting with WebP2 as Successor t... by chrismorgan on Monday November 16, 2020 @10:26AM (#25112813)
If it was framed that way, they’d be wide open to accusations of anticompetitive behaviour—using their position of operating their various web services and making a browser to push functionality that benefits just them into their browser, which no other company would be able to do.
Re:Google Is Already Experimenting with WebP2 as Successor t... by Spivak on Monday November 16, 2020 @11:48AM (#25113840)
That paints kind of a weird perspective on open source and open formats. Companies develop and release lots of OSS specifically because it benefits them to write and maintain it. Twitter made twemproxy for their own scaling issues but then released it to the world. I don't see a difference with Google here.

"We made this thing because it solves a problem we have, and we're giving it away so it might solve the same problem for you" doesn't seem nefarious.

Re:Google Is Already Experimenting with WebP2 as Successor t... by asah on Monday November 16, 2020 @08:33AM (#25111401)
I think that ship has sailed a long time ago... software needs regular updates for security patching, so adding new formats is not the big deal it once was...

If nothing else, just provide a slow-but-correct decoder that translates the format to a long term stable format (e.g. PNG).

Re:Google Is Already Experimenting with WebP2 as Successor t... by ttfkam on Monday November 16, 2020 @09:43AM (#25112210)
An in-app decoder would translate to pixel data. Why would you re-encode to a different format like PNG that's optimized for storage when rendering to a display?
Re:Google Is Already Experimenting with WebP2 as Successor t... by asah on Sunday November 22, 2020 @10:22AM (#25178100)
Sorry I meant recode to pass into tools/libraries that no longer support the older format.
Re:Google Is Already Experimenting with WebP2 as Successor t... by TonyTrapp on Monday November 16, 2020 @08:54AM (#25111601)
That doesn't work so well with the whole ecosystem around it that actually creates those files. Think of graphics programs that still don't support WebP or cameras that cannot simply be updated... oh wait, smartphones already killed those.
Re:Google Is Already Experimenting with WebP2 as Successor t... by detaro on Monday November 16, 2020 @09:02AM (#25111701)
Why does it matter if a camera supports WebP or not?
Re:Google Is Already Experimenting with WebP2 as Successor t... by anonuser123456 on Monday November 16, 2020 @09:55AM (#25112358)
At Google, you can't get promoted by steering the ship.