AM radios in cars only cover the small intersection of people who don't already have an emergency kit containing an AM radio, but do happen to be in a working vehicle during a disaster.
It's useless for anyone who's outside of a vehicle for whatever reason - eg vehicle is damaged, out of fuel, had to be abandoned, or was not available nearby when the disaster struck.

And what about people without a car?
Also if you've been forced to abandon your car due to the disaster, there goes your radio too since you can't easily remove it and wouldn't be able to operate it even if you could. A portable radio can be taken with you.

Depends on the nature of the disaster.
High winds can easily destroy solar panels.
Thick clouds will massively reduce the amount of power they can produce.
Thick smoke would be even worse.

At least he didn't write "I hope you are well"...

AM radio has very poor audio quality, you wouldn't want to be listening to music that way.
And your problem is trying to stream. Modern phones can have more than a terabyte of capacity, more than enough to store anything you'd want to listen to at a reasonable quality level.

I don't believe teams has e2ee at all?
In any case you typically don't need or want that in a work environment. Encryption between client and server is enough, as the org controls the server and wants to be able to view/monitor communications between its employees.

Any company that was using something else before teams came along also complains bitterly about teams - it's different and in many ways inferior.

I know several places that switched from slack to teams, they all universally hate teams.

The fact that this approach is catalytic rather than requiring a binding agent seems positive in terms of longevity and not being directly depleted by repeat exposure; but I'd be curious how durable the material is under real-world conditions(clothing that gets hard wear tends to get hard washes) and also how specific it is. 'Organophosphate' means something moderately specific in the context of chemical warfare; but a lot of fairly prosaic compounds are, technically, 'organophosphates'(like DNA and RNA when held together by phosphodiester bonds); and this would be considerably less helpful in practice if it is busy chewing up the genomes of random soil bacteria; and markedly less helpful in practice if there's a "do not perturb the nanites in your clothing if you want them to not migrate into your cells and start mitigating the harmful effects of your DNA" user notice on the treated article.

This doesn't seem like a lie, a NIC is in a pretty good position to knock something off the network if it feels like it and the 'bluefield' devices have enough punch onboard to run some rules regarding whether or not to do that; but it seems like a wild exaggeration of how helpful it actually is.

If you actually have a set of rules that detect your bot being wicked it will presumably save you some CPU time to run them on the NIC rather than having the host CPU watching the traffic; but the hard part is the set of rules that detect your bot being wicked.

This is basically the equivalent of adding a firewall and claiming that you've solved network security. Yeah, the firewall is pretty well placed to block malicious traffic; defining 'malicious traffic' is left as an exercise for the reader.

Support for Office 2016 and 2019 ends October 14th of this year; I assume that the feature is dropping now; rather than either 20 years ago as part of ECMA-376 and eventually in a live product for either Office 2010 or 2013, or never if they didn't want to do that, in order to draw a hard line under the utility of those?

It otherwise seems like a kind of weird time to do it. In principle what a 'cell' is has never really had an obvious mandatory scale: it has essentially always been relevant that a 'cell' existed in relation to other cells, so that something like an array could be a row; but it has also long been allowed and encouraged to do things like substring operations that acknowledge that cell contents are 'larger' objects that contain smaller ones; and are not automatically spilled out for that reason alone. Not clear that the pragmatic use case for spreadsheets would ever have supported some sort of 'any data type that implies it can be decomposed into elements shall be' rule, strings getting broken up into substrings and so on; but it's also not clear that the pragmatic use case is going to be much clarified by a single cell being n levels deep of lists and arrays of lists and arrays being a fully supported thing rather than something you hack on by shoving JSON into text cells or whatever.

It definitely seems like asking for confusion when some, but only some, "excel spreadsheets" have cells that are arrays, potentially of arrays, while others have rows of cells with contents that, at least formally, are not acknowledged as arrays.

Unsoldering the ram chips and replacing them takes some effort and skill, and then you end up paying for 2 sets of ram chips - the old ones (which you cant do anything with) and the new ones. Given the effort and cost involved, this is only worth doing if:

1) the higher ram model is heavily marked up vs the incremental component cost so buying the ram yourself is significantly cheaper.
2) the same ram is genuinely expensive, but much cheaper ram is available and still works without noticeable side effects

If it's all about markup then it's pure profiteering and screwing the users.

If the only way to undercut the official models sufficiently to make the whole operation worth doing is by using inferior components then there is *some* legitimacy to trying to stop this, but the approach is wrong.
If someone is going to the effort of replacing the ram chips with something inferior to resell the unit then they're not going to think twice about shipping with an old bootloader either, or modifying the bootloader to bypass the check, or working out how to get the bootloader from the genuine larger ram models to work on the lower ram models etc.
Sure the hacked/old bootloader might get noticed later if someone tries to update it and bricks the device, but low quality ram or a poor soldering job could just as easily brick the device too. By the time this happens the seller will be long gone anyway.

This DOES hinder repairs. For instance you might have multiple faulty units with different faults so you take the working RAM from unit A which has a faulty CPU, and switch it onto unit B which had bad ram.

That's the sort of curious thing about this announcement: at least in theory(I assume things are uglier in practice) the X1 parts that they shipped for windows-on-ARM/Copilot PCs already use UEFI/ACPI in line with what MS wants for booting Windows.

That obviously doesn't mean that there's a working GPU driver; or that naive power management doesn't cause the system to run at 90% of maximum power and hammer the battery flat; but the theory was that the last gen was already doing the "big kid ARM that has embraced PC standards" thing; very similar to the 'standards base' that ARM encourages ARM server part vendors to use.

I'm always a little curious what the thinking/strategy is with the Chinese outfits. I don't necessarily expect much from the OrangePi guys; they ship a surprising number of different SoCs, including multiple architectures and multiple vendors, for their size, so are likely to be mostly at the mercy of the SoC vendors; but is the situation for someone like Allwinner such that people who want linux to work on their stuff could be a resource for them and they are just not taking advantage of that very well; or are they actively annoyed by GPL-related claims and really just want to shove minimum-viable android out the door as cheaply as possible to win cheap tablet tenders and really do not want to hear from SBC hobbyists.

SOP at Qualcomm. It has been literal years of hammering on them by Google and basically every Android handset OEM to even keep parts that ship with android support in support for more than a few years(I think the current timeline, at least for 'snapdragon 8 elite' flagship parts, is a princely 8 years from release; and that is with the 'project treble' stuff that attempts to reduce the number of changes that might potentially need to be supported). Especially with the, um, raging success, of Copilot+ AI PCs they are probably ready to pretend that X1 never happened and call it good. I'm not even sure how long the windows support on X1 is expected to last.

Exactly this.
I bought a PS3 because it advertised both the ability to play games *and* the ability to run linux.
Some time later i was forced to make a choice between continuing to run linux by retaining the old firmware and not being able to play online or play newer games, or update the firmware to play those games while losing the ability to run linux (and losing access to any data in the linux partition too). I have not bought another sony product since then.