If that Russian Trump piss tape does exist, the other people involved are almost certainly underage.

That’d be Chris Christy.

Lithium batteries are often -30 to 80C, but that’s just saying what’s possible to squeeze some kind of voltage out of them. Basic principle is that the colder it is, the harder it is for chemical reactions to happen, and thus this will affect all chemical batteries to some degree.

Encryption everywhere isn’t about the individual content. By making it ubiquitous, it’s harder for bad actors to separate the encrypted data they want from the one’s they don’t. If only special content is encrypted, then just the fact that it’s encrypted is a flag for them. It also makes it much harder to ban. It’s pretty much impossible to ban the algorithms in TLS at this point. Too much depends on it.

What, you don’t love downloading a zip file that contains an msi (which is perfectly capable of internally compressing much of its internal data)?

If you’re going to lecture about “maturing”, then maybe don’t start by jumping to conclusions based on the first sentence.

There’s often an alternative way of looking at things that can make seemingly inconsistent positions become consistent. In this case, it’s control. They want to control children and they want to control women’s bodies. How this happens morphs in each situation, but the underlying goal is there.

I am absolutely certain that experts have looked at it, and come to different conclusions.

I’ll even go as far as to accept that there is no scientific consensus.

And what reference do you have for that? A recent one, because as I said, the economics have totally changed in the last 30 years.

Nuclear power doesn’t really produce co2

Concrete does. Reactors need a lot of concrete. A lot.

Renewables are still not ready to deal with base load in a power grid long term

Which doesn’t matter. Base load exists because it’s cheap to make power plants that stay at the same level all the time. The economics of that don’t apply to renewables.

Nothing, nuclear power will buy us time

Utterly untrue. It’ll take 10 years to deploy a single new GW of nuclear. That’s not buying time.

You don’t have to pay to “prove” I’m right. You just have to accept that experts have looked at this, and nuclear does not need to be part of the conversation. Not beyond keeping whatever we have already, at least.

Oh, fuck a book, aahhhhhh

The newer sodium batteries are comparable to LFP batteries from a few years ago.

Nuclear power should be expanded, a lot, it is the only realistic way to replace fossil plats for base demand.

This 90’s talking point against Greenpeace is no longer valid. The economics have changed.

https://www.cambridge.org/core/books/no-miracles-needed/8D183E65462B8DC43397C19D7B6518E3

The other side of that is matching supply to demand is basically instant. You pull power from batteries and they give you more (provided they’re not at their safe limit). There’s always a lag in getting turbines to spin up and down, and so there’s a non-trivial mismatch time.

While you’re not wrong, sodium batteries coming on the market have 200 Wh/kg. This is comparable to where LFP batteries were a few years ago. That means the newer sodium batteries are about as good as what’s in lots of EVs right now.

They are dirt cheap, don’t have the fire safety issues as some lithium chemistries (not all lithium chemistries do that), and sodium is abundant.

There is an actual legal principle of laws simply going out of date, even if they don’t explicitly have a sunset date.

https://en.wikipedia.org/wiki/Desuetude

It’s more common in the UK, where you have 1200 year old laws banning wearing of sandles on Thursdays, but it pops up in other Common Law countries, too, including the US.

Right.

As an example, Klipper (for running 3d printers) can update its configuration file directly when doing certain automatic calibration processes. The z-offset for between a BLtouch bed sensor and the head, for example. If you were to save it, you might end up with something like this:

[bltouch]
z_offset: 3.020
...
#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.
#*#
[bltouch]
z_offset: 2.950

Thus overriding the value that had been set before, but now you have two entries for the same thing. (IIRC, Klipper does comment out the original value, as well.)

What I’d want is an interface where you can modify in place without these silly save blocks. For example:

let conf = get_config()
conf.set( 'bltouch.z_offset', 2.950 )
conf.add_comment_after( 'bltouch.z_offset', 'Automatically generated' )
conf.save_config()

Since we’re declaratively telling the library what to modify, it can maintain the AST of the original with whitespace and comments. Only the new value changes when it’s written out again, with a comment for that specific line.

Binary config formats, like the Windows Registry, almost have to use an interface like this. It’s their one advantage over text file configs, but it doesn’t have to be. We’re just too lazy to bother.

Is a very good idea providing much needed fixes to the JSON spec, but isn’t really what I’m getting at. Handling automatic updates in place is a software issue, and could be done on the older spec.

If anything, we need to double down on freight. Get all the long haul trucks off the highways that we can.