Except that many large enterprises have seen this movie before with Broadcom buying things like CA. They already know the product development vanishes and support gets thin while prices quickly escalate. Then shelfware is bundled into an "all or nothing" deal so they'll keep bleeding you until you get every scrap of their shit out of your stack with them hoping you take the bait.

We've almost got every last scrap of their products peeled out of our business. Never again.

That's really the only use I have for my one echo device. I consume their prime music content and pipe it out to a small amplifier for stereo speakers and a small subwoofer in my garage so I have music to listen to when I'm being a gear head. I guess if I HAD to, I could use a raspberry pi or something like that to do the same, but this just works and I'm lazy.

When you move up the school hours you do the same thing to work hours. Problem solved.

Comparing the Starship prototype to a battle tested workhorse that's been in production a lot longer isn't particularly useful. When Starship proves that it is a safe platform for humans, great. Until then, why not use it to launch cargo/satellites if the economics are sound?

If you dont want your kids going to school in the dark just change the school hours.

Prepare for a new head of the FTC.

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.

It's unfortunate. The Orange Pi 5 Plus on paper is nice. When I bought all the bits for about US$300, that got me 8 fairly fast RK3588 ARM cores, 16GB RAM, dual 2.5GB ethernet, decent video, decent npu (for then), native nvme, 256GB emmc storage, 1TB nvme ssd and a small case with active cooling. It would be a LOT more expensive to roll that together today, but it's working ok as a headless home media server. I suspect it would also be fine for a desktop device for many people (no gaming, but it plays 4k video just fine and is perfectly acceptable for consuming web content).

http://www.orangepi.org/html/h...

A great opportunity missed by those folks.

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.

It'll be interesting to see if it gets more enthusiastic support from Qualcomm than we saw from the various Chinese arm variants that took YEARS to get anything more than the basics working without a lot of mystery kernel blobs on an older kernel. It'll also need to arrive at a sane price point.

I've had an Orange Pi 5 plus for almost 3 years and it only JUST now works without a lot of hand holding on current Debian/Ubuntu and I think the npu is still not quite there yet.

Like spending that same money to build vocational schools for the skilled trades that are in short supply. I know...not as cool and exciting, but I think we need 10,000 more welders a lot more than we need 10,000 more tech bros.