Note that this all is around the Compaq BIOS case, and a part that keeps getting glossed over is the finding that the part being protected, the ABI interface, was not substantial enough for protection.

Software that is more substantial beyond just ABI/API is likely to be considered differently.

Note if it documents the full code body and translates that back into code, that may be treated differently. The BIOS documentation covering inputs and outputs, but not how those things are processed are one thing, but if it is a full prose description of the execution steps of a function, well that's different. In short, the LLM is likely to carry over the substance of the implementation in the prose, and break the whole promise of 'clean room'.

While true, mixing up 'reign' and 'rein' is a pretty non-LLM move. We see the words as very similar, but token wise they don't have anything to do with each other, though maybe muddied by copying human mistakes.

In the man page I see:

RETURN VALUE
              On success, a pointer to the hashed password is returned. On
              error, NULL is returned.

Yeah, crypt() *should* return a NULL pointer, *not* some arbitrary string when there's a fault. Entirely musl's bug.

I would hardly call profit taking when a big gain is *guaranteed* a "moron" move.

At some point it really will be the top of the market.

Besides, it's less about performance and more about investor sentiment. You are predicting the other humans level of investment, *not* the financial health of the company, unless you are in it for the dividends of course, but relatively fewer people are thinking dividends. The market value of those projections are already baked into the price today.

But even by the standard of financial results, the projections are subject to change. If some of the neoclouds fold up, then the projections evaporate.

On the ATM card, it's about cost reduction.

On the PC side, it is, fundamentally, a platform that emphasizes flexibility versus mobile that screws flexibility while locking down. So it's mainly about how far a malware could get running against the wishes of the device operator, rather than what a user could do to misbehave. I'm not taking the trade-off, but there is at least a rationale.

More to the point, for them to have the authority to even theoretically facilitate such volumes of transfer, regardless of software compromises...

Given the way big publishers have already made games a cesspool of microtransactions, online-only operation even for single player experience.... Retro game interest is *long* overdue.

AI slop is merely the latest 'slop' in an industry long rotting.

I'm waiting for Super Intelligence II Turbo: Hyper Fighting Championship Edition.

The CEO sees other tech companies getting giant boosts and is pissed that isn't him. Line going up for other companies more than his.

When in doubt, blind alignment to the hype of the day should, potentially get there. No room for nuance or actual vision to what would capture the indicated missing value, AI should just provide it... somehow.

Why the hell bother using an AI when you could just type what you would prompt into the comment directly?

To the point you put into the LLM, it's perfectly plausible that someone wiring up an LLM to their email and their bank account suddenly are at huge risk of a scam working. Whatever problems exist in the technical implementations the fact remains that folks greasing the wheels for their money to go out autonomously incur the risk of..... their money going out autonomously...

Well the answer is of course they are out of touch and I don't actually have a 'right question', I just wanted to fit in.

No, it's just the sort of thing that the UEFI design kind of does.

You load a bunch of stuff that all initializes, just in case it might be needed. One of the key optimizations in some UEFI implementations is trimming down the things that get loaded based on an early assessment of whether this or that would be relevant to the expected boot. For example, hit key to enter setup and suddenly it has to load all the things to make sure all the various menus work.

Kind of like setting up the NIC in the OS before anything asks for network access, so that every network access isn't burdened with having to set up the network access. If the driver is already loaded then a variety of potential UEFI network code could just use it (PXE, HTTP, iSCSI, various crap from vendors like pre-OS firmware download)

We will see, but *so far* Ford has not been as aggressive about that sort of thing as BMW or Chevy. The BlueCruise requires actively curated lidar maps, so at least they have a rationale for that being an ongoing subscription. The other subscriptions are similar, updating GPS maps (who needs those with phone) and data connectivity (but if you have a phone, you don't need it). So far they haven't charged for remote vehicle services which arguably could be charged for the SIM service and/or server infrastructure they have.

Note that their point is they state they had the car's onboard system also provide AC to the load side, making the cost lower to incrementally make it a backup unit.

Most solutions provide DC and a separate inverter is required to power the house.

Presumably this came from the desire to consolidate things and wanted to do the 'plug power tools into the truck' feature and the delta to get to 'car side house scale inverter' was appealing.