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.

From my math, once you account for inflation, Silicon Valley (and broader tech industry) compensation has declined about 23-30% since 2000, relative to the national average. I know multiple companies where it's basically been flat since 2012, particularly for support roles - $90-100k then is only making $105-110k now in the same roles (with some of the same people, granted, but also new blood).

Considering how many foreigners from specific countries I see in places like Omaha, NE, I'm pretty sure it's not just a problem in Silicon Valley.

That may be true, but it's irrelevant.

They'll 500 500+ Americans from Division A while hiring 500 Indians to Division B.

And then the next quarter, it's fire 500 from Division B (all Americans, mostly white men), and then hire 500 Indians into Division A - because they had a shortage, don't you know.

How was it not fraud?

H1B is/was intended for worker shortages: for roles you couldn't fill domestically. It was not supposed to decrease the wage of the role, but (in theory) keep it at parity. It was always a ruse, but that was the premise.

If you're firing people and then hiring others at a fraction of the pay, you're literally abusing it. You've applied under false premise. That's fraud.

MOAR POWAH = faster magic smoke production! Efficiency!1!!

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.

This 'study' was clearly constructed to create narrative, not to do actual science.

"The study was conducted with 189 people."

And what was the distribution of men and women in that sample? Because that's a very important criteria.

I promise you the results would be significantly different with all-male vs all-female groups, and depend heavily on the attractiveness of the 'male' or 'female' AI persona (assuming it had visuals).

The study said half did Joanna and half did Micheal, and were asked to rate and pay the bot. Since all participants did not do both, one question is how did you ensure they graded the results equally. In other words, if presented the same results from a gender neutral or unidentified bot, would everyone give the same payout or would it vary by participant. I looking at the results, the men paid teh robot and chatbot more and than he women, which to me indicates a difference in how value is perceived that may carry over into the gender role test; where oddly women paid both bots more than men, flipping the results. Interesting study, but I thnk there is more at play than just gender bias creeps into AI bots as well.

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.

Oh JFC.....

What's next...Trans-Bots and DEI for underserved Bot minorities?!!? H1-Bot....?

It sounds interesting from a hardware perspective ....

....but "Windows"? Ick...no thanks.

The need for them came from relativity, but the atomic clocks needed to be able to handle such fine corrections are based on the hyperfine transition of 133Cs. You're not getting very far on atomic clocks without particle physics

Okay Felicia.