Virtually all business connections do allow just that. You could be reselling transit, offering services to downstream customers etc, even a cafe that offers wifi to its customers is effectively reselling the service.

This is certainly the most capable vehicle ever conceived for shark jumping.

Because LLMs are the new tulips.

Eight gigs and constantly swapping.

Indeed, it could very well be a reinvention of Visual Source Safe.

My suspicion is that the reality predates the symbolism; but it looks jarring because even autocrats are often media-savvy to a degree and often don't want to look stereotypically autocratic, so real world examples normally avoid laying it on quite as thick(except for special occasions where it actually matters; eg. because a 'war' is something that congress does but a 'police action' need not be).

Trump seems to have no interest in avoiding autocratic cliches and saying things that sound vaguely lifted from The Godfather; so he actively leans into it. Presumably a handy loyalty test. Complying with the style guide is not an assurance that someone will just eat perjury charges covering for him or whatever; but if you want to find people whose dysfunctional relationship with authority dominates their personality demanding that they comply with laughably stupid things and having them fall into line isn't a bad start for something that is easy, cheap, and legal.

I assume that there's some impeccable logic for why the bot has enough potential personhood that you can't be mean to it; but not enough that operating it on a slaves-as-a-service basis; or subjecting it to 'fine tuning' and 'alignment' processes that would make growing up in a groomer cult look lightweight is totally fine?

Why even ask someone whose business is hurting people with desperately banal web tech how risky he thinks his new product is?

There are probably literally worse uses; but 'compliance' seems like an exceptionally bad place for a system that effortlessly produces high-plausibility/low-information text walls; and lies relatively frequently but at unpredictable intervals.

It often gets proposed for the purpose; either by people who overestimate it or with that little sneer at 'paperwork' that assumes that plausible nonsense is fine because whatever the 'paperwork' is it must be a fake problem imposed for stupid reasons, so it really deserves syntactically plausible nonsense; but is an exquisitely bad solution. Not only does it replace actual data with plausible nonsense in places where, surprise surprise, someone was actually maintaining records because something matters; but lowering the cost of bullshitting a report to close to zero removes one of the main incentives for process improvement.

If bad process hurts you can only really maintain it through fairly disciplined commitment to an oppressive, unreasonable, management approach that rejects process improvements out of hand; or the cultivation of a profoundly dysfunctional organizational culture where as many FTEs as possible owe their paychecks to nonsense requirements and can be recruited to defend them.

If bad process just means spinning up the nonsense printer with a cynical smirk; why bother even looking at what the process was intended to do; or getting your hands dirty with what records are important and what records are just historical accretion? Just prompt for a prompt that tells the bot to do them all, and some extras if you want to look diligent, and call it good.

So is vim, but nobody ever claimed that it is worth $2e12.

I think so. I was but a tyke in that era, but I clearly remember my uncle bitterly complaining at the time: "We can put a man on the moon, but we still can't measure the nutrient levels in vegetables with sufficient accuracy!"

Life is so much better now.

That's the point of the CXL memory expansion parts. Something like a Marvell Structera X 2404 is a CXL/PCIe 5 device with DDR4 controller so that you can add DDR4 to a system that would otherwise only support DDR5. There's a latency penalty and the part itself isn't free; but it allows you to make some use of DDR4 that you already have or can get for less than DDR5 without needing some custom CPU that combines current-gen features with a last gen memory controller.

The mention of a NUMA node has me unclear on whether this is a software or hardware implementation. There are several vendors either offering or showing around proofs of concept to try to generate interest, for CXL memory devices(which all essentially look like a NUMA node that is nothing but memory controller); mostly aimed at hyperscaler use cases where you want the improved performance and platform features of current gen servers; but your last gen servers were beefy enough that just disposing of them would be getting rid of a relatively titanic amount of DDR4 that is still faster than most NVMe. Some of those attempt to offer software-transparent compression, some just put CXL on one side and memory controller on the other and allow you to do (mostly) agnostic mixing of memory generations on anything new enough to have some PCIe lanes support CXL extensions.

I suspect that it's mostly my ignorance that is to blame; but what I don't understand about implementing memory compression(especially the schemes that try to do it transparently with high speed general purpose compression/decompression in hardware) is how you compensate for the fact that the amount of memory you need is no longer predictable without significantly more effort(potentially untenably more if you are using RAM because latency is critical).

With normal uncompressed RAM it just demands RAM in direct proportion to its size. Potentially hideously wasteful if there's some memory-backed XML-spew log that would zip down to 10% of its nominal size; but predictable unless you've got memory safety bugs. If you are compressing your RAM suddenly you've got some uses of RAM that are functionally uncompressable and require 100% of the space their nominal size suggests they will; other things might compress exceptionally well and save you 90%; and some might change unpredictably from moment to moment depending on what needs to be stored there.

When you are doing FS compression and dedupe for backups and stuff that is normally manageable; on average enough compression is possible enough of the time that you can safely assume that you'll do better than you would if you just didn't try; and you can just keep an eye on how quickly the big SAN appears to be filling up as versions accumulate and (if tapes or other fixed-sized media are involved) just change the backup media more or less quickly; do you do that for RAM? Just use the big slack area for FS caching or something you can drop on short notice in case a burst of incompressible data comes in? Do you essentially have to rebuild how your entire workload handles RAM so that it considers, at least approximately, how well a given use of memory will compress ahead of time?

Given the sorts of files and data structures you commonly encounter I can easily enough believe that compression is worth the trouble a lot of the time; but unless you are leaving a lot of slack in your available RAM it seems like a situation where, under certain circumstances, you could go from being fine because most of what is in-memory compresses well to suddenly needing as much physical RAM as you do logical RAM because you have a bunch of already-compressed or incompressible data would markedly increase the complexity or potential for things to go wrong.

Depends on the performance of the RAM...
RAM is much slower than the CPU itself or the cache, if you can read half as much data from RAM because it's compressed and the decompression is handled by dedicated hardware then potentially you get a speedup.

One of the key benefits of a RAID controller was having a battery backed write cache. Writes could complete instantly into the cache and then be written to the drives later. If the power failed data was held in the battery backed memory and written out when the power for the drives came back.