Comment Re:data || GTFO (Score 1) 74
But on Linux? The software RAID controller was faster. The job is I/O bound, not CPU bound.
it can be accessed in a read-only fashion with little delay; just the cost of hardware-offloaded compression..
This reminds me of the days when we were using hardware RAID controllers...even though it was all done in hardware, it seems like they were somehow always slower than the Linux software RAID controller. I never figured out why. What I am saying is, I don't trust the hardware-offloaded compression to be faster without seeing the data.
It's frustrating because the Democrat party while they don't lie to you
They lie too. Half of them are the Epstein class.
That's why I hate both parties. Not only that, I hate the mentality that causes people to create parties (ie, have to find someone to bully)
What the fuck am I even reading?
The lament of a crypto-bro.
No one is doing anything illegal here
They are doing illegal things. They know that qualified candidates exist, but conduct the search intentionally in such a way that candidate will not be found.
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.
McCarthy was right, the Venona intercepts prove Soviet spies had infiltrated the government.
That wasn't the thing people didn't like about him.
He was wrong for doing a witch hunt, punishing people without due process of law.
The other firms being suspended from the program include Capgemini, Cognizant, HCL, Infosys, Tata, and Wipro.
Those are the contractors.
I'm open to other suggestions but I have yet to hear a single one that is both viable and actually works.
I don't really oppose H1b, but arrest one CEO who is hiring people illegally, and this will stop.
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.
You do not have mail.