The_Decryptor

Musk has started talking about an ill-defined idea called “universal high wealth.”

iirc Musk’s whole idea was that every person on earth would buy a robot or two of his (or ideally rent them), send them off to work jobs while they stay at home, then split the combined income with Tesla.

Of course, it’s never explained why the companies wouldn’t just buy/rent those robots directly.

https://www.youtube.com/watch?v=ZQkzS969Lc4

It’s real, but probably not an issue in practise.

If it does actually turn out to pose a problem, then just disable secure boot on those systems, not like it’s really securing anything at that point.

AMD has its own mix of issues with Vulkan between RADV (mesa), AMDVLK, and AMD’s proprietary driver on a per-game basis at times.

Good news, they’re going away. AMD is focusing entirely on Mesa now.

If everyone has moved on from 32bit, and the old stuff doesn’t change, where is the maintenance requirement?

The problem is that it’s not old unchanging code, people want the latest supported version so they can still run their 32-bit binaries with the latest supporting libraries.

And if the upstream developers don’t consider 32-bit support important, then it falls on the distro maintainers to patch the code to keep it running in these situations.

I always thought it was purely a hardware limitation, but reading up on it I found it’s actually just “virtual 8086 mode” that was dropped, 16-bit protected mode is still available even when running the CPU in “long mode”.

So it rules out DOS apps, but 16bit Win 3.x apps should still run. But it’s probably a compatibility minefield, and even MS decided it wasn’t important (iirc the only thing they kept around was support for 16-bit app installers, but by internally swapping them out with 32-bit versions when run, since it was apparently common for 32-bit 9x apps to still use 16-bit installers so they could show a proper error message when run under Win 3.x)

It seems to me that 16-bit applications are already basically broken with 32-bit wine if you’re running a 64-bit kernel, by default it places extra restrictions over what the hardware already does to prevent apps from loading 16-bit code entirely.

https://gitlab.winehq.org/wine/wine/-/wikis/FAQ#16-bit-applications-fail-to-start

Guessing that’s why they don’t feel it’s that important to continue supporting, seems a VM is the future for these apps.

WINE’s WoW64, does not work for all games.

Ok but is that because of fundamental limitations, or just because of bugs?

One’s easier to fix than the other.

So how the OS already catches links to e.g. YouTube and offers to open it directly in the app, it could also do that for apps that weren’t installed and it’d just download and run them automatically. One of the examples was Vimeo, instead of loading the website it’d download a cut down variant of the normal app and load the video in that instead.

The idea was to push people towards using apps instead, but now Google control the web they can just make that their app store instead, so native apps aren’t as relevant anymore.

Also, compared to something like the Switch? I don’t see MS remotely bricking these devices if you run “homebrew” on them.

It might not have sit well with the fans - he might take a big swing and miss - but at least I felt like he was trying to create art instead of merely making money.

Same, I actually loved how his story had Rey as a nobody whose choices and actions were what made her important, SW has way too many special bloodlines, prophecies, and chosen ones.

Then Abrams does a 180 in the sequel 😑

I still hate that god damned dagger.

For a while Google let you blacklist domains from search results, fantastic feature so of course they killed it off.

Never knew until I immigrated to the US. And even then, its merely a brief mention on it and calls it “communism” (its not lol) and then the teachers proclaim its why “communism” is bad, USA constitution rule of law blah blah.

That’s when you bring up Kent State

A single user mastodon instance has the same issues, any hashtags you can see will be from users you already follow. You need to subscribe to a relay to see more posts (Which GTS actually currently doesn’t support, so you need to follow tags from something like https://relay.fedi.buzz/)

They’d run afoul of the whole “editing your own article” restrictions.

They really want to promote their AVIF format, and supporting JXL would hinder that (Since JXL is a much nicer upgrade path from JPEG/PNG than AVIF is)

Like you can transparently go from JPEG to JXL and back with no loss, which isn’t possible with AVIF. And PNG to JXL gives you a smaller file, while it’s usually the opposite with AVIF (Unless you get lucky, as lossless AVIF can be beaten by a BMP in a ZIP file). There’s also the issue of speed, AVIF is slow to encode compared to other formats (And while hardware decoding is possible, it’s also geared towards video, so the quality is often lacking, and can sometimes be slower than plain software encoding)

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.

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.

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.

That’s because those adapters aren’t DACs, they’re straight electrical passthrough adapters.

I’ve got an actual USB DAC, a relatively cheap one, and it was still close to $50.

Edit: Doubled the price in my memory.