But if we accept that it currently ignores any upper-bounds checks greater than v3, that's interesting. Does that imply that once Python 4 is available, uv will slow down due to needing to actually run those checks?

I think the same thing about a lot of code, too. Sometimes you really are just hammering out boilerplate. But a lot of times even writing test code is a great opportunity to realize the main code could be improved. But the LLM probably won't tell you that.

> Roman-era mining activities increased atmospheric lead concentrations by at least a factor of 10, polluting air over Europe more heavily and for longer than previously thought, according to a new analysis of ice cores taken from glaciers on France's Mont Blanc.

A lot less than modern technology manages, but a lot more than nothing. And that with a much smaller population.

https://phys.org/news/2019-05-roman-polluted-european-air-he... https://en.wikipedia.org/wiki/Ruina_montium

Do you also wonder how we'll get rid of used coal power plants, massive piles of toxic fly ash, and tons of pollutants from natural gas plants? Because so far the answer is not good.

I believe you're talking about Earth, and the person you're responding to was talking about Mars. At least I don't think Mars had an oxygenation event or fossils?

She pointed out it was on a sign on the counter that I was looking at that moment, and had also been there when I dropped the car off the day before.

From TFA:

> To make things even more complex, many of these large companies are not traded publicly on the stock market, meaning their total number of holdings is not easily available to the public. Because Invitation Homes is publicly traded

1. Write "logging" data (observability, whatever) 2. Someone else starts using that to drive behavior 3. Change your logging, because it's just logging right? And stuff breaks.

To state it another way, anything you're emitting, _even internal logging_, is part of your API/contract, and therefore can't be changed carelessly. That problem is the same no matter what technology you use.

Usually the hard part is collecting the numbers and defending their validity.

A few random reasons:

- The Oculus goggles become uncomfortable and sweaty fairly quickly

- They use Fresnel lenses and (I think...) foveated rendering, which means you really only get sharp view straight in front of you. Not where your eyes are looking, where your head is pointing. So looking at the other screen, or even scanning text, means moving your head.

- The awareness of your surroundings is basically zero so it's easy to "lose" your mouse. Or, in my case I was using a wireless keyboard, and I could misplace it. There is a passthrough mode, but the resolution is garbage and it's annoying to get in and out of (in theory you can tap the headset, in practice it works maybe 50% of the time)

Probably some other stuff I'm forgetting...

Anyway, all that said I think there's potential that AV could do it significantly better. No idea if they actually did do it better, though.

But Wikis are useful for things that are shared, or that are not tied to a particular product, or don't exist in the product yet. eg - "What's the temporary workaround for this bug?" - "How do I get started as a new employee?" - "What information do we need on customer requests?" - "What's the team process for handling escalations?" - "Here's the preliminary design for this new feature"

You still need someone to update those docs, but it's nice if, eg, the manager (or product/project manager) who isn't in Git all day can do it easily instead of asking a dev to do it.

Yes. Even before we get to full V2G, managed charging provides a helpful degree of flexibility.

An EV is a giant battery (several times the size of a Tesla PowerWall, for example) that happens to move sometimes. The battery can be used for other things when the car isn't moving - and it will be.

It's unfortunate that EVs make the most immediate sense in high-density urban settings, but those same settings have lots of people who can't use the simple kinds of charging infrastructure (eg, Level 1/2 chargers).

Pretty sure I've seen that the cells themselves are already a minority of the total cost of a solar installation. Most of it is labor, permitting, framing (as you mentioned) and other ancillary things. Dropping the price of PV cells is all to the good, but it's not the limiting factor for mass adoption of PV.

Increasing the efficiency of cells would help more, since you could get more power from a given amount of the other supporting stuff.