4 ms·
Yep, teenagers like Facebook and Adobe - oh wait. Maybe Google is now flexing its anticompetitive muscles now, isn't it?
by zinekeller 4y ago
Yep, teenagers like Facebook and Adobe - oh wait. Maybe Google is now flexing its anticompetitive muscles now, isn't it?
- brookst 4y agoI must be failing to understand your comment. The people complaining are FSF, and no matter how hard I squint, I cannot see how fair competition could require Google to be the first one to support a standard that literally nobody else supports.
- zinekeller 4y ago> The people complaining are FSF Nope, not just FSF. The Chromium team have prototyped JXL, but removed it initially for unknown reasons (https://bugs.chromium.org/p/chromium/issues/detail?id=1178058#c183 https://bugs.chromium.org/p/chromium/issues/detail?id=117805...). Engineering teams including but not limited to Adobe, Facebook, Intel and Shopify have complained about its abrupt removal. Chromium developers have subsequently said that it was "due to low interest" (despite piles of messages from engineering teams both in leading companies and small groups saying otherwise). > I cannot see how fair competition could require Google to be the first one to support a standard that literally nobody else supports. First, Adobe products have just included JXL. Second, It's because Google is pushing for AVIF, which was extended from AV1. While it has some advantages (as essentially extended version from AV1), it also has a lot of disadvantages: https://news.ycombinator.com/item?id=35590516 https://news.ycombinator.com/item?id=35590516. No one said to remove AVIF in favor of JXL and in fact there are instances where AVIF is the better choice (animated images due to its interframe support) but instead to support JXL regardless of Google's support of AVIF, and some people have seen it as forcing Google-favored AVIF instead of considering all formats developed (like how WebP was rammed a decade ago).
- SquareWheel 4y ago> but removed it initially for unknown reasons Just an FYI, they gave their reasons in comment #84 of the thread you linked.
- brigade 4y agoAdobe didn't support WebP until 2021, they're the poster child for not supporting a format until it's popular enough that they need to add support.