Their servers go down because they DDOS themselves demanding more cert renewals than they can support. The blog certificates expire and browsers refuse to load your cat memes.

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.

You wrap them in plastic carefully first. The cameras are perfectly safe in the protective concrete packaging.

I remember listening in on a great phone call to a network provider about sending someone to pick up their expensive Cisco router. It ended with "in 30 days, it's going in the dumpster.

I personally 'uninstalled' another router by disconnecting the fiber cables...with side cutters. 2 months later, they actually tried to bill us for bandwidth we supposedly used from the completely disconnected router. We sent them a picture.

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.

I ran this through the translator. "Having a dedicated home with Prime Video allows us to build on that legacy with unprecedented global reach and a broader commitment to the Television Academy and our mission throughout the year."

It came out "Jeff offered more money."

The difference is that if you pay people to monkey around with things, you get a non-revocable perpetual license to the result. With license rental, you get a perpetual bill. It's the same rent trap as individuals get stuck in but with less excuses.

Yes, and the reason is that they stupidly painted themselves into a corner and never thought about an exit strategy. Had they been thinking about the possibility that they might one day need to migrate from the beginning, it would be much cheaper to do so now.

That's the thing about painting yourself into a corner, a little better planning at the start can always avoid it with little to no additional effort.

that's cool, but wtf does that have to do with this post? did you just read the word "AI" and jump to the comments to share your deep wisdom?

I've said it before, but I'll say it again for those who arrived lete: If you give an AI agency of any kind, imagine everything you ask of it to be appended with "by any means necessary", because that' how it will interpret it. Slander, doxxing, and murder will definitely NOT be off the table even if you explicitly forbid them. That's the problem.

Honestly it should be called string toolbag. It contains some math that might (or might not) one day be useful in constructing a theory but it honestly has never actually been predictive enough to call it a theory.

A little of each. Banks in the U.S. actually maximized inconvenience by being closed any time most people actually had a decent opportunity to go to the bank, but it worked out somehow.

We already have string theory for that:-)

While the line of reasoning is sound, it's more or less a non-theory of exclusion.