Speaking based on my own PC in that era: it had 512MB RAM and the video card was capable of running FFVII PC version with hardware drivers, so there was some very modest and primitive 3D capability buried in there somewhere. I believe the CPU was a ~500 MHz P3, so I’ll grant you that one, and the one about RAM speed. Well, I did only claim they were “somewhat similar”.

Wi-Fi 7 Marketing is Lying ~About it’s Biggest Feature~

Truth in advertising is pretty much nonexistent these days. Assume they’re lying until proven otherwise.

Except that it isn’t really the first iteration of any of those things. Java did most of 'em more than a quarter century ago: browser-embedable, multiple languages could target the JVM, and, yes, sandboxed—the only issue was startup (not runtime) performance. That wasm doesn’t share those startup performance woes makes it useful, but not revolutionary.

As for tiny environments, a typical desktop system from around 1999 is somewhat similar to a Pi Zero W in terms of ability.

At that point, you’ve put multiple man-hours into analyzing the response required to placate it, and it isn’t a “cheap” device anymore. Easier to return it.

If they’re auditing that many of them, there will be a queue, too.

Only in the US. But they do tend to be measured and sold by volume (rather than weight) in contexts like farmer’s markets and pick-your-own operations.

I didn’t think the horse was still intact enough that you could find any hide.

Ugh. I hope that there being a use for the little bastards now doesn’t make people breed them on purpose.

Python and Ruby have both had various repo issues too.

I’ve never heard of anything similar with Perl, but that may partly be because applications for new developers who want to join CPAN still appear to be processed by humans, with up to a couple of weeks lag. The time inefficiency plus the language being less popular probably makes it an unattractive target.

There’s nothing wrong with ARM. Qualcomm, on the other hand . . .

In the worst case? On ebay, as a “For parts/not working” model with a reasonably intact exterior. Might take a bit of patience.

Actually, it’s an extinct genus of land snail. Really. Wikipedia told me so.

It isn’t just annoying, it often breaks for people on less-popular browsers. Plus, it requires you to run Cloudflare’s Javascript. You think this outage was bad—what do you think would happen if someone slipped them a bit of malware?

I doubt most of them could stick with the Gentoo installation procedure for long enough to make it to a usable system.

Conditions on freeways are usually more controlled than conditions on surface-level roads, and Waymo’s accident record isn’t bad, unlike Tesla’s. I suspect that this isn’t going to generate any post-debut news stories of much significance. (If something bad and avoidable does happen, though, Waymo is 100% accountable—no handwaving it away.)

As with all the other alternative browser-related projects, I wish them luck. It isn’t easy just keeping pace with the details of current standards documents for rendering webpages—climbing up from zero (even if they’ve already made considerable progress) has got to be even more difficult.

For what it’s worth, Pale Moon can still be built for 32-bit Linux ( fish through contributed builds, or build your own). Sufficient for many, many sites, although a few will break or require workarounds.

“Artificial Intelligence” doesn’t actually want anything. It has no agency. Meta/Facebook wants to sell you stuff while the world burns, but that’s nothing new.

The question for me isn’t whether or not there’s a difference that I might be able to see if I were paying attention to the picture quality, it’s whether the video quality is sufficiently bad to distract me from the content. And only hypercompressed macroblocked-to-hell-and-back ancient MPEG1 files or multiply-recopied VHS tapes from the Dark Ages are ever that bad for me. In general, I’m perfectly happy with 480p. Of course, I might just have a higher-than-average immunity to bad video. (Similarly, I can spot tearing if I’m looking for it, but I do have to be looking for it.)

On top of that we shouldn’t distribute compiled binaries for the x86 and ia64 chipsets; instead program code should be distributed like .wasm, in a hardware-independent way, and compiled on the target device. That would enable that hardware can use any chipset it wants and there are no software incompatibilities because of it.

You’re describing Gentoo Linux . . . which is not especially popular among Linux distributions even though it runs on just about anything. There may be a reason for that.