What a funny tangent to go off on.

JXL was dead. Apple is who brought it back to life[1], and the only reason Chrome resurrected JXL, and now Firefox followed their path, is because Apple pushed JXL support to a billion plus devices.

I know people like complaining about Apple, but there's a "read the room" kind of moment where people just seem to either not know the context or are just knee jerking.

[1] Worth noting that Apple used the reference implementation, libjxl, and that project still remains the reference implementation with the Rust port being experimental (and of course Apple deployed JXL support over a year before the Rust port even existed). Maybe they'll switch to it at some point, but it's a bit premature to complain about.

▲

ChoosesBarbecue 3 hours ago | parent | next [-]

I believe Firefox was the first to put out a standards position about adopting jxl if a Rust implementation happened. Chromium only aligned their position this year I believe, prior to that, it was a complete rejection.

Which is to say, Chrome followed Firefox here.

(Yes, I know Google Research implemented jxl-rs, but then, they also implemented jxl. Chrome’s position appears independent of them.)

▲

spartanatreyu an hour ago | parent | prev | next [-]

> JXL was dead. Apple is who brought it back to life

No, it was actually the PDF Association.

They added JXL to the PDF standard.

If google wanted to maintain support for displaying PDFs, they would need to add support for JXL.

	▲	NewJazz an hour ago \| parent \| next [-]
		* wanted to maintain support for displaying jxl images that are embedded in PDFs
	▲	llm_nerd an hour ago \| parent \| prev [-]
		The PDF consortium added JXL to the PDF spec two years after Apple deployed support to billions of devices. To anyone ackchyually paying attention to the JXL spec, lamenting that this superior format wallowed in obscurity (largely, it should be noted, because Google dumped it, and so many others just follow the leader of Google), Apple actually completely changed the path of the format's adoption.

▲

deadbunny 5 hours ago | parent | prev [-]

I wasn't complaining, it's a factual statement made sarcasticly.

Things apple do because apple do:

- make a mouse you can't use while charging it

- gets bored of the power inefficency L of x86, makes the fastest arm cpu that causes x86 manufacturers get serious about power

- hey, those f keys? what if useless strip

- decades ahead in panel tech and refuses to compromise

▲

concinds 4 hours ago | parent | next [-]

I don't see what this has to do with the topic, sorry.

	▲	wongarsu 4 hours ago \| parent [-]
		Their point is that Apple is the Nintendo of computing. They don't care what others do, they just do their own thing. Which produces some great things and some stupid things. They also don't care whether you think what they are doing is great or stupid, they just continue doing their thing Which then tracks back to the beginning of the thread: the correct answer to whether apple will adopt jxl-rs or keep libjxl is "who knows, no point trying to predict them". Which is not a value judgement How you square all of that with the iPhone regularly copying features Android had for years is your decision. Might be a symptom of the same, might be that this all was an entirely inaccurate description of Apple

▲

_joel 4 hours ago | parent | prev | next [-]

That useless strip could play lemmings and doom, it wasn't all bad

▲

tombert 2 hours ago | parent | prev [-]

> make a mouse you can't use while charging it

I'm not one to usually defend Apple-ism, but it always felt that this was such a nothing-burger. The mouse charges in like fifteen minutes and lasts for weeks. I don't have a work Macbook (or job :) ) right now, but when I did I would just occasionally plug it in while I went to the bathroom. It really was not nearly as annoying as everyone said it was.

	▲	spartanatreyu an hour ago \| parent [-]
		Remember all those times you needed to make a change to something a few minutes before it was submitted/presented? Imagine if you couldn't, because you needed to charge your mouse first.