And there you are wrong and quite obviously so. I will not even argue that point

Can't argue the point so you'll pretend to be taking some sort of high ground.

Your claim is obviously stupid, and since it's obvious I'll say why. Unlike you, who cannot say why which is why you didn't.

People, ordinary people go between multiple roles in their life while remaining the same person. Within a job people get promoted and may have some management duties, which may well involve deciding pay levels to some extent. Sometimes people strike out on their own and do contracting and start a company at which point they have full control over what they offer subcontractors or employees.

And even for those who do not people still get other jobs done via contractors, like plumbers, electricians etc, at which point they decide they pay levels as much as any business owner.

You like many people are absolutely bending over backwards to reinterpret the results to be what you want.

You know I've been on this thing for almost 30 years and never figured out the "upvoting" and other fancy finctions people often brag about...

You must have missed that "firehose" link that's been at the top for 25 years or so. I wouldn't brag quite so hard about missing it, personally.

Kinda like a /. post.

And those corrections require atomic clocks.

You think LLMs would write "Slashdot doesn't have table support, so it's hard to do side-by-side well, but:"? You think LLMs like writing sentences that end in conjunctions that express incomplete thoughts? Do you think LLMs write "high frequences", "naively pairs", call H.265 X.265 (I was thinking of what you refer to it as in ffmpeg), imbalanced parens after "lacks motion vectors",etc?

Don't get me wrong, I am a LLM user, I absolutely do use it sometimes for search, fact checking things I'm writing, spelling/grammar checks (clearly not that time, lol), etc. But I write my own posts.

Ordinary people do not decide about the pay of others in actual reality.

Yes they do. Management/employers are not some special class of person.

So your reply has nothing do do with the pot it was replying to then. So why reply then?

Interesting that you immediately jumped to censorship. Why is that?

The muh freeze peach crowd are about the worst defenders of free speech I've ever met.

Speech is powerful and dangerous, which is why it is important and needs to be free. Pretending otherwise is to diminish it and erase the need for it to be protected.

Slashdot doesn't have table support, so it's hard to do side-by-side well, but:

JPEG XL advantages:

Licensing:

JPEG XL: Fully royalty-free (Open source / Apache 2.0)
HEIC: Proprietary patent minefield (MPEG LA, Advance, Velos; royalties apply)

Legacy JPEG Migration:

JPEG XL: Lossless, reversible bitstream transcoding (~20% smaller); fast enough for real-time web servers
HEIC: Lossy re-encode only (generational quality loss; cannot reconstruct original JPEG)

Fine Detail & Textures

JPEG XL: Retains sharp text, fine lines, subtle textures, and film grain
HEIC: Video-derived coding (HEVC / X.265). Tends to smooth out high frequences and smudge grain.

Software Encoding Speed

JPEG XL: Extremely fast; highly parallelized SIMD architecture
HEIC: Exceptionally slow and computationally expensive in software

Software Decoding Speed

JPEG XL: Fast, lightweight multi-threaded CPU decoding
HEIC: Heavy CPU overhead (without using hardware acceleration)

Progressive Rendering:

JPEG XL: True progressive decode; smart saliency algorithm to focus bandwidth on critical details first.
HEIC: None; full file must be received and decoded before display

Lossless Compression
JPEG XL: Dedicated modular mode; vastly outperforms PNG and WebP
HEIC: Ill-suited; you basically have to try to do lossless compression with an inherently-lossy format

Bit Depth & HDR

JPEG XL: Native HDR; up to 32-bit floating point per channel
HEIC: Typically capped at 10-bit or 12-bit integer

Max Dimensions & Scaling

JPEG XL: Up to 1B x 1B; efficient viewport/crop loading without full decoding
HEIC: v5.2, 4096x2160; v6.2: 8192x4320; a tiling hack allows up to 16384 x 16384

Channels & Color Spaces:

JPEG XL: Arbitrary color spaces (hyperspectral); unlimited extra channels (alpha, depth, thermal, masks, CMYK, etc)
HEIC: Rigid container; limited auxiliary channels and standard video color spaces

HEIC advantages:

Rollout / acceleration:

JPEG XL: no dedicated hardware acceleration (thankfully, it's not as important because it's so much more efficient). Software adoption still rolling out.
HEIC: Hardware silicon (ASICs). Default capture format on modern iOS/Android; native capture in Sony, Canon, and Nikon cameras

Video:

JPEG XL: Supports animations (GIF/APNG replacement), with some optimizations** (it's not just a series of stills), but lacks the full set of optimizations that a proper video codec has.
HEIC: Container naively pairs full HEVC video tracks and audio with video.

** - JPEG XL can store up to 4 reference frames in a buffer, with multiple blending modes from the references (add, replace, multiply, etc); has subframe bounding boxes ("dirty rectangles") for when only part of a frame changes; invisible frames; modular deltas (differences between frames); etc. However, it lacks motion vectors (e.g. detecting a feature drifting across a scene and simply having to encode "move it" (followed by any needed deltas). So it's great for "GIFs", but if you wanted to encode a full movie, it'd be significantly larger than e.g. HEVC.

Anything that challenges your assumptions must be a joke. Therefore you never need to change your mind on anything!

Look, I use HEIC, but JPEG-XL is just better.

* Royalty-free
* Lossless transcoding of legacy JPEGs to immediately reduce their sizes by ~20% (fast enough that you can have webservers do it in realtime)
* Better fine detail / high frequency data representation for the same bitrate. HEIC was designed for video and simply is not as good at stills.
* Faster decoding
* MUCH faster compression
* True progressive decoding - and not old-school blocky progressive decoding, but using a smart algorithm that restores coarse detail (particularly focusing on parts of the image that the eyes immediately focus on) first, then progressively adding in finer detail that the eyes take more time to notice later.
* Vastly better lossless compression
* Better colour depth and native HDR (up to 32 bit per channel)
* Up to 1B x 1B pixel images (again, useful for scientific and engineering applications), with efficient loading (don't have to load and decode the whole 1B x 1B image at full resolution to view it)
* Arbitrary colour spaces - you can even use it for scientific hyperspectral imaging. You can include e.g. alpha, depth maps, thermal data, selection masks, etc etc.

It's just a better format for stills. It's annoying that it's taken this long to get support to take off (because it takes ages for most people to update their browsers), but I'm really glad that it's starting to.