Hmm, two decades ago perhaps. We must be getting old because it doesn't seem like that long ago.

It's more like "dictionary entry of the year". Some things where the two words have to be used together for a specific meaning have dictionary entries, such as speed bump, for example.

Then everyone will start using it as an excuse to attack other people. Especially the cops - they hate being filmed. They will claim it was "aggressive" and justified violence.

A guy called Graham Linehan was just convicted of smashing a girl's phone, when she filled an interaction where she asked him why he called her a "groomer" on twitter, and worse. It was the right judgement, he had no need to do it, and mere annoyance can't be enough or everyone will be smashing stuff they dislike.

If there were better APIs they could do that. An API for sensors, with a maximum safe limit supplied for each one. When a BSOD happens, it could do a little memory test on the affected area.

It's been done before, taking pictures on the subway, and those were done by photographers or people trying to get into photography. Such pictures are easily found by doing a simple search.

It's about perception. When someone is wearing these glasses they are looking at you with their eyes. When someone is taking a photograph, the camera is between you and them. It's obvious what the person is doing.

Didn't all of these problems come up with Google Glass over ten years ago? In fact the term "Google Glasshole" was coined for people using Google Glass to record people who didn't want to be recorded. While it is legal to film in public, they did not seem to understand why people did not like it. This user seems to fit that mold.

No but they were experimenting with germanium. My understanding is that researched stopped because while they could get better results with germanium, the problem was how to use it germanium practically as it is 1.6ppm in the Earth's crust while silicon is 282,000 ppm.

That's like the situation where one of my neighbor's dogs pooped on my lawn. Which neighbor was it? Was it the one that I see conscientiously pick up their dog's poop every time on their walks. Or the neighbor that lets their dog roam around the neighborhood with no leash? Your argument would be the conscientious one did it to frame the other neighbor. Because . . .sympathy and support? I do not believe Europe needs any more justification for sympathy and support for Ukraine.

Consider Russia indiscriminately attacks civilian targets, I would bet Russia hitting it by accident or on purpose. It is hard to know at this point.

One major difference, assuming you've got full platform support(should be the case on any server or workstation that isn't an utter joke; but can be a problem with some desktop boards that 'support' ECC in the sense that AMD didn't laser it off the way Intel does; but don't really care); is that ECC RAM can (and should) report even correctable errors; so you get considerably more warning than you do with non-ECC RAM.

If you pay no attention to error reports ECC or non-ECC are both rolling the dice; though ECC has better odds; but 'proper' ECC and Linux-EDAC support will allow you to keep an eye on worrisome events(normally with something like rasdaemon, not sure what other options and preferences there are in terms of aggregating the kernel-provided data) and, unless the RAM fails particularly dramatically and thoroughly, will give you much better odds of knowing that you have a hardware problem while that problem is still at correctable levels; so you can take appropriate action(either replacement, or on the really fancy server systems, some 'chipkill'-like arrangement where the specific piece of DRAM that is failing gets cut out of use when deeemed unreliable without having to bring the system down.

Will it be cash or a participation trophy like his FIFA medal?

Gotta distract from Epstein or how we drop bombs on fishing boats over alleged drugs and then pardon a convicted drug kingpin.

No what that means is higher production costs do not necessarily map 1:1 to higher price in the end product in every instance. Sometimes the cost is eaten by the manufacturer in terms of profit. Sometimes the manufacturer can change the product to offset the increased cost. For example, cheaper materials, cheaper labor, etc. Now I am not saying they are good changes but that would be one way higher production cost is not passed onto the consumer directly in terms of price.

While the article focuses specifically on memory prices, the AI boom could also cause PC CPU and GPU prices to go up which affects everyone. Currently fabrication at TSMC and Samsung are limited with companies like NVidia and AMD booking orders years in advance. To chase profits, NVidia and AMD will shift more of their orders to AI chips if they haven't already done so. That means fewer consumer CPUs and GPUs and thus higher prices for consumers as there may be shortages.

I don't see how it would help the situation to buy cheaper phones. The issue is RAM prices are going up. That affects expensive flagship and cheap phones alike. In fact, you may not be able to buy a cheap phone as manufacturers are going to prioritize selling the flagship phones first as that gains them the most profit.

Sometimes you'd get a BSOD that was a fairly clear call to action; when the error called out something recognizable as the name of part of a driver; but that is mostly just a special case of the "did you change any hardware or update any drivers recently?" troubleshooting steps that people have been doing more or less blind since forever; admittedly slightly more helpful in cases where as far as you know the answer to those questions is 'no'; but windows update did slip you a driver update; or a change in OS behavior means that a driver that used to work is now troublesome.

Realistically, as long as the OS provides suitable support for being configured to collect actual crash dump material if you want it; it's hard to object too strongly to the idea that just rebooting fairly quickly is probably the better choice vs. trying to make the BSOD a genuinely useful debugging resource; especially given how rare it is for the person with useful debugging ability to happen to be at the console at the time of crash(rather than just an end user who is ill equipped to make sense of it; or a system that mostly does server stuff, quite likely not on actual physical hardware, where nobody has even touched the physical console in months or years; and it's more or less entirely useless to display a message there; rather than rebooting and hoping that things come up enough that management software can grab the dump files; or giving up and leaving the system in EMS so that someone can attach to that console.