lonjil

9 ms·

61.
by lonjil 3y ago
But we do know where it is, to quite good precision. We know how much or how little dark matter is present in different galaxies, which matches quite well with the amount of dark matter that must've been present in the early universe t
62.
by lonjil 3y ago
Just the opposite. Sure, DM was proposed when some observations didn't match predictions, but do you think scientists liked that? Do you think they just accepted it? They did not. No one liked DM, and many people tried to disprove it
63.
by lonjil 3y ago
I guess I should say, take up lots of space unless you're OK with lower quality. In any case, gainmaps are entirely unrelated to the 8 bit vs 10 bit question. The more range you have (gamut or brightness) the worse 8 bit is, regardless
64.
by lonjil 3y ago
> but it's absolutely ass for UI. uhh, no it isn't? And gainmaps suck, take lots of space, don't reduce banding. Even SDR needs 10-bit in a lot of situations to not have banding.
65.
by lonjil 3y ago
> "We've never had to wear helmets before, why start now?" > We live in the future. We have memory-safe languages now. We're allowed to use them. You won't get in trouble from anyone, I promise. That's wh
66.
by lonjil 3y ago
Pretty much every codec in every browser is written in an unsafe language, unfortunately. I don't see why JXL should be singled out. On the other hand, there is a JXL decoder in Rust called jxl-oxide [1] which works quite well, and has
67.
by lonjil 3y ago
But the server doesn't necessarily have unlimited time to encode those images. Each of those 1 million images needs to be encoded before it can be sent to a client.
68.
by lonjil 3y ago
Actually, if you already have loss, you should try as hard as possible to avoid further loss.
69.
by lonjil 3y ago
Actually, they did try QOI for the photographic images: > Not shown on the chart is QOI, which clocked in at 154 Mpx/s to achieve 17 bpp, which may be “quite OK” but is quite far from Pareto-optimal, considering the lowest effort se
70.
by lonjil 3y ago
I misrecalled. While the Google patent is a lot more general than the Microsoft one, it doesn't apply to most uses of ANS.
71.
by lonjil 3y ago
I think JXL has been seeing adoption by apps faster than Webp or AVIF.
72.
by lonjil 3y ago
Whichever is more pessimistic. So for the axes in this article, the first one. If you have an option on the "bad" side of the Pareto curve, you can always find an option that is better in both axes. If a new option is discovered t
73.
by lonjil 3y ago
And the one you're replying to is also talking about battery life. The energy needed to display an image for a few seconds is probably higher than the energy needed to decode it.
74.
by lonjil 3y ago
8-bit can have banding even without "HDR". Definitely not enough. 10 bit HDR video is becoming more common, and popularity for images will follow. Adoption is hampered by the fact that Windows has bad HDR support, but it all works
75.
by lonjil 3y ago
I wonder if the text would be consistent enough for JXL's "patches" feature to work well.
76.
by lonjil 3y ago
I believe they were referring to that WebSocket issue, not JXL.
77.
by lonjil 3y ago
The Microsoft patent is for an "improvement" that I don't believe anyone is using, but Internet commentators seem to think it applies to ANS in general for some reason. A few years earlier, Google was granted a patent for ANS
78.
by lonjil 3y ago
Real-time encoding is pretty popular, for which encoding speed is pretty important.
79.
by lonjil 3y ago
Well, lots of things other than JXL use ANS. If someone starts trying to claim ANS, you'll have Apple, Disney, Facebook, and more, on your side :)
80.
by lonjil 3y ago
> And I suppose the Chrome folks have the telemetry to know how many people set that damn flag. How is that relevant? Flags are to allow testing, not to gauge interest from regular users.
81.
by lonjil 3y ago
Daala's and Thor's features were supposed to be integrated into AV1, but in the end, they wanted to finish AV1 as fast as possible, so very little that wasn't in VP10 made it into AV1. I guess it will be in AV2, though.
82.
by lonjil 3y ago
> In most domains proprietary specifications form the backbone of everything. A lot of governments refer to ISO standards, which by default are not open access. Standards documents being behind a paywall is not at all the same thing as s
83.
by lonjil 3y ago
Hardware acceleration of image decoding is very uncommon in most consumer applications.
84.
by lonjil 3y ago
Prior art makes patents invalid anyway.
85.
by lonjil 3y ago
Lossless AVIF is just really quite bad. Notice that how for photographic content, it is barely better than PNG, and for non-photographic content, it is far worse than PNG.
86.
by lonjil 3y ago
If you don't have progressive decoding, those metrics are essentially the same.
87.
by lonjil 3y ago
I have heard that it will see a proper standalone release at some point this year, but I don't know more than that.
88.
by lonjil 3y ago
> Of course it didn't, it wasn't designed to be either the fastest nor the best. Just OK and simple. Yet in some cases it's not completely overtaken by competition, and I think that's cool. Actually, there was a big p
89.
by lonjil 3y ago
> you want Chrome to re-add jxl behind a feature flag? Doesn't seem very useful. Chrome has a neat feature where some flags can be enabled by websites, so that websites can choose to cooperate in testing. They never did this for JXL
90.
by lonjil 3y ago
Mate, you're literally pulling something from your ass. Chrome engineers claim that they don't want JXL because it isn't good enough. Literally no one involved has said that it has anything to do with patents.

More ›