My house is a relatively normal size (1800 square feet), and it still takes more than three full minutes for water in my shower to reach full temperature when I run it straight hot. If I also turn on both faucets in my bathroom, I can get that down to about twenty or thirty seconds, which is barely tolerable.

At my mom's house in Tennessee, the distance the water has to travel is comparable, but it takes only ten seconds or so.

It's a huge downside to all the water-saving showerheads and faucets that were forced upon us here in California decades ago. We waste a lot of time and energy to make up for a water shortage that exists only because of decades of politicians being short-sighted and kicking the desalination can down the road over and over so that the money doesn't get spent on their watch.

Translation: A company that has the potential to benefit from regulation by squeezing out competitors wants more regulation.

I'm not saying they're not right, just that it seems awfully convenient for a company specializing in pumps that recirculate data center water to want efficiency regulations that would push customers towards their most efficient (and thus presumably most high-margin) pumps.

Instead of having your hot water fan out in a tree, you wire it like a token ring with a return pipe, where each faucet only has a short bit of pipe between it and the ring. Then, you have a pump to circulate hot water through the ring-shaped pipe network. That way, it takes half a second to get hot water instead of half a minute or more.

Sure. I'd imagine most hardware vendors will want it. I'm just saying that the wording, at least as described in the summary, is... problematic at best.

Not really. It's more like requiring all vendors who sell cash registers used in restaurants to support checking photo IDs because some restaurants also serve alcohol.

There's no safe way to prove your age to a website. Any scheme requires trusting some arbitrary third party that could secretly be the government doing timing comparisons between the verification and DNS queries and stuff to unmask anonymous users. At least with operating system or browser vendors, they presumably have a strong commitment to minimizing the risk of someone publicly posting "John Doe just visited sexwithseaturtles.com" or whatever.

It's not really that terrible. If you're going to do age verification, you have two choices: browser or operating system. All else is all but guaranteed to be either a privacy disaster, a usability disaster, or both. And either way, every operating system needs to support multiple users, or the "I used dad's iPad to browse porn and buy firearms" problem makes the verification useless.

And major operating system or browser vendors that cater to the general public should make it available by default, because doing so prevents the "You downloaded the AdultCheck module, so you must be a pervert" logic that some people might use to attack people.

What's terrible is the idea of mandating that it be performed at the OS level, rather than just mandating that the OS doesn't get in the way. Browser-level verification is actually far preferable, because there's no need to bake that into an authentication framework when you can just send it out to a browser window. Leave that tiny bit of integration complexity to the companies that actually require it. But this only works if the OS supports multiple users, so that the browser's cookies and storage are not shared across multiple users.

For devices that don't have multiple users, baking it in at the OS level really is the only way, but it could just as easily be solved by baking it in at the browser level and changing the OS to allow multiple users per device. Unfortunately, such technical details are way too subtle a point for most lawmakers to understand, so obviously they did it in the most wrong way possible.

Wait 'til they realize that Android is distributed under a license that allows people to copy, redistribute, and modify it.

As usual, a law created by people who didn't think of the consequences then got modified to fix some of the worst consequences, but because they still did not think of the consequences, the modification created different consequences. And this is why we need better lawmakers.

Maybe, but the problem is that the electronics have to run at those temperatures and not have solder joints start popping, or other fun failures.

As far as I know, it is just real-time. And it didn't even slow down at the flashing red light. So either it recognized that someone was waving it on or it didn't see the flashing light at all.

I *think* that number actually is counting them, though it's hard to be certain. I'm pretty sure servers are outnumbered by PCs by a large margin.

Cameras and LIDAR. I am not a self-driving car engineer, but from what I understand, it seems likely that it is possible to detect water with even just cameras, at least under the right circumstances, and with cameras plus LIDAR under a lot more circumstances. But doing so would require proper training data; it's not like there's a "Ooh, that's water" recognizer built into the hardware or whatever.

More to the point, they would have to train it how to recognize that some particular sensor return pattern (e.g. zero LIDAR reflections off the ground) is a problem, and do so in a way that doesn't over-correct for flooded potholes, an inch of water in the street, etc. Presumably, detecting water is the easy part; detecting the depth of water is the hard part unless you know exactly how high the curbs are.

I'm a little spooked when I see Tesla FSD beta demos where the car plows right on ahead through slightly flooded streets as though there's nothing there. It makes me wonder whether it saw it and ignored it or just didn't see it. It's the same feeling I got this morning when someone was signaling me to go ahead at a flashing red light and FSD beta (12.6.4) went right on ahead. I wonder if it somehow saw the hand gestures, or if it just didn't see the flashing red light at all.

That's what makes all this stuff fun.

Any hardware or device driver engineer will tell you that every hardware problem, once shipped, is a software problem. :-) (Translation: Hardware bugs, once the hardware is in the wild, have to be fixed with a software workaround.)

Nothing in self-driving cars is a quick fix other than geo-blocking something. You have to train a visual or LIDAR recognition model to recognize the problem situation and then train the path finding model to flag it as a bad path. How hard that is for this particular case, I have no idea. And there's probably other stuff beyond that; I'm not an expert in this area.

Yeah, there's not enough crack in the world for that to make sense. The cost-to-orbit is well documented. Artemis 2: $4.1 billion for a launch that can lift 95 tons to LEO. SuperHeavy/Starship: $90 million for a launch that can lift 150 tons to LEO. Ignoring minor details (e.g. that nobody is willing to expend a SuperHeavy to do trans-lunar injection), the reality of the matter is that the cost per ton to orbit for NASA rockets is 72x what it is expected to cost for SpaceX rockets.

And that's consistent with Falcon Heavy costs, too, so you can't hide behind "Yeah, but SuperHeavy and Starship don't work yet", because unless your payload is huge, SpaceX is still almost two orders of magnitude cheaper.

That never made much sense to me. The power requirements and cooling requirements for a data center in the vacuum of space would be completely infeasible.

The most any commercial satellite has ever dissipated, as far as I know, is only low-double-digit kilowatts worth of heat. Three high-end NVIDIA AI cards per satellite would basically fully max out a typical satellite's heat dissipation, without factoring in any of the heat produced from communication hardware, energy storage, solar heating, or heat dissipation from the computer that's powering those GPUs.

A large data center would likely include one or more clusters of 100,000 GPUs, not three. A typical communications satellite is on the order of 220 square meters. Do the math, and you get 7,333,260 square meters, or 7.3 square km. This translates to a radius of .76 km, or a diameter of 1.52 km. Sure, it might not be not as dense as a meteor of that diameter, but it would still be really, really bad to deorbit something that size. I would not be surprised if the resulting dust cloud causes crop failures for years on a scale that would wipe out a sizable percentage of human life.

If, by data center, you just mean an edge cache like Cloudflare or Akamai, then it might be slightly more feasible, but even that is pushing the limits of my suspension of disbelief.