[subfay]

This piece gives a hint where Trivago as a company went with Holacracy. The lack of focus is so obvious and seems to let individual developers create some work which is not just poorly worded but also nonsense:

Why should anyone test a format which is used by just two browsers with a very small market share and which will be never adopted by the company with the biggest market share (because Google has WebP). JPEG-XR is DOA and nobody should care and waste time on this (except the OP gone astray).

I like that there is a tl;dr right at the beginning though.

[robin_reala]

I think that’s unfair though. It’s not necessarily about percentages; potentially they could easily be seeing a few tens of millions of monthly visits from IE and Edge, and if putting in place an automated system to convert images to a (theoretically) more efficient system had increased conversions they’d be really happy for the payback.

Thinking about it, assuming they’ve got a WebP output for Chrome already this could be as simple as adding one more build step with a different encoder, and one more negotiation rule on the CDN.

[jbreckmckye]

I'm not sure I'd be quite so blunt, but I do agree with your argument in the main: this is so low on the list of priorities that I can't help but wonder if someone at Trivago thinks they've run out of any actual revenue-generating development work.

It indicates to me that either the inmates are running the asylum - that devs are being given too much leeway to pursue personal interests - or (and?) that Trivago's day to day work is proving so dull that developers in some teams are inventing R&D work just to stay sane.

[subfay]

Yeah my tone was a bit to harsh and I didn't want to insult anyone but I am still wondering that nobody at Tribago gave him this feedback. However and hopwfully this useless piece of work leads him to some other more relevant stuff.