The_Decryptor

joined 7 months ago
[–] The_Decryptor@aussie.zone 5 points 16 hours ago (1 children)

It’s unclear why Google stuck with PNG for HDR screenshots instead of a format supported by Ultra HDR such as JPEG.

Because for good lossless HDR you've got a grand total of 2 options, PNG and JPEG XL. And Google don't want people to know of yet another use case for JXL.

[–] The_Decryptor@aussie.zone 8 points 1 day ago (1 children)

Edge is also following Chrome with the V3 rollout unfortunately.

[–] The_Decryptor@aussie.zone 4 points 2 days ago

"Fans claim it may offer an improvement" isn't exactly a definitive statement.

From what I understand the research does actually show little to no improvement for either mode, which is actually a bit odd because we know the eye performs better the brighter the surroundings (Since it causes the pupil to contract, increasing the depth of field)

Maybe it's a sign that we just need more research into the effectiveness in interfaces.

[–] The_Decryptor@aussie.zone 5 points 2 days ago (2 children)

Unfortunately, it'll still take a while, this chip from MS only has 8 qubits on it.

And the largest number ever factored by a quantum computer is... 21, and that record was set 13 years ago.

[–] The_Decryptor@aussie.zone 25 points 2 days ago

Or just plain union organizers.

[–] The_Decryptor@aussie.zone 2 points 4 days ago

I’m not sure if there is just some “point of diminishing returns” or whatever where JPG actually becomes more efficient or what.

There is, but it's at high quality levels. If you're using WebP for thumbnails or other lower quality situations (Which was the original intended use) then WebP will give you better quality than JPEG for a given filesize.

For lossless uses it's even better, the format is much more limited than PNG, but in the common cases it beats it.

[–] The_Decryptor@aussie.zone 1 points 5 days ago

I take that there isn’t much motivation in moving to 128 because it’s big enough; it’s only 8 cycles (?) to fill a 512 (that can’t be right?).

8 cycles would be an eternity on a modern CPU, they can achieve multiple register sized loads per cycle.

If we do see a CPU with 128 bit addresses anytime soon, it'll be something like CHERI, where the extra bits are used for flags.

[–] The_Decryptor@aussie.zone 3 points 6 days ago (4 children)

I think CHERI is the only real attempt at a 128 bit system, but it uses the upper 64 bits for metadata, so the address space is still 64 bits.

[–] The_Decryptor@aussie.zone 17 points 6 days ago (1 children)

It's kind of like Wikipedia, you have to cite the original source (State or council maps) rather than a 3rd party source.

The map data for my suburb is all kinds of wrong on Google Maps, there's a park around the corner from me which is marked as a house for starters, blindly copying that into OSM would be a disservice.

[–] The_Decryptor@aussie.zone 8 points 1 week ago (8 children)

The ones that fall out of the sky rarely hit anything. Ukraine is vast.

By definition they hit something, it's just not considered important when said something is a patch of grass or a medium sized rock.

[–] The_Decryptor@aussie.zone 5 points 1 week ago

I think the biggest issue would be a lack of interfaces to the C side code, they're slowly being fleshed out and each one enables more functionality for the Rust modules.

e.g. the test Ext2 driver a MS dev wrote last year after enough of the filesystem interfaces got hooked up

But even then, I don't think the maintainers would accept one that replaces the existing C driver, that'd break non-Rust builds and architectures, and that's a sure-fire way to get Linus on your case. Best you can hope for is one that complements a C driver, and even then I think you'd need a good reason to have two drivers for the same hardware.

view more: next ›