> Memory defaults to half of host memory

That's the most expensive part of the whole transaction, b/c AFAIK, RAM is then dedicated to the VM. It can be swapped out, I suppose, but that's not great.

That said, colima still has the expensive VM that upthread is mentioning.

It's not entirely free; the cost is that the resulting binary will no longer run on processors that lack the instruction. Which, admittedly, is ≈2007 or older. But still! I have a 2012 CPU still in service, and as much as I'd love to obsolete it, gestures at the price tag of RAM these days.

… a 2012 CPU is surprisingly competitive relative to today's tech, too, I'd add. The gap between 2012 and 2026 is nothing compared to the equivalent gap between 1998 and 2012: 1998 is like 500MHz single-core, 32-bit. 2012 is 4 core, 8 hyper threads, 64-bit, 3.5 GHz. (… perhaps more remarkably, my next-oldest machine, a 2017 laptop, is only 2.8 GHz, with the same 4(/8) cores. It also uses like half the power, too. That's mostly the "laptop" bit, though.)

(That same CPU is also incapable of "v3".)

* My Subaru runs ads for Sirius XM. (Ad, on the infotainment screen. While the car's in motion.) I did not pay for my car to run ads, obviously, and obviously that was never mentioned by the dealer, ever, before or after purchase.

And forced-arbitration, which is also entirely one-sided.

… but as you say, idiots are lining up.

Why? Why should I become an example, or a leader? To be blunt: why do companies think I should do that additional work, without additional pay?

So yeah, definitely the "more work" part.

A distributed WAL (to survive a machine death) would also probably be something I'd want, and … something I'm not sure you're getting directly from SQLite.

> As a government regime, do you want to build an effective surveillance system where health data on large numbers of suspects can be pulled into a data fusion system at the push of a button, once a judicial framework for rubber-stamping is in place?

Sure, and I'm right there with you that people should protest frameworks for judicial rubber-stamping. But HIPAA is like the only privacy law in America, basically, and having it mandate that medical data is encrypted can be good on its own.

While there are standardized formats for medical data, many are so ill-adopted that building some sort of surveillance system would be a monumental task; the bulk of data I've worked with has been in poorly documented, non-standard formats.

> Both of these are easier when smaller vendors are forced out and larger vendors are the only ones left standing

Clearer regulations and standardized, interoperable data formats benefit smaller players.

Uh … sure I would? Why not? The top bracket was 70% in the 80s. So that 61% is still a fair bit short of what it was then. (And the 80s isn't the highest point, either.)

IDK if it would be a good idea or not, but I'd entertain the debate, certainly. To state that this is unarguable, though, well…

While true, this is a molehill, not a mountain, of a bar, like "coding once in a while". I'm doing mostly SRE work, and this syntax has no trouble sticking in my head, and I encounter it pretty regularly? (And heck, most of my work these days is in Python, so there I get the >=,< syntax and yearn for the ~mines~ caret, and I still recognize it?)

If you're actively developing a codebase, this definitely isn't going to be arcane trivia.

… an assumption that something happened is not a definitive statement that it did happen, only that we're assuming it did, because it could happen, or perhaps here, that because the major was bumped, that it is legal, according to the contract given, for it to have possibly happened in a way that we depended on. They're not saying that it will/must; "assume a major version is incompatible" is not at odds with what you've written.

  monolith -> openai
  monolith -> langchain-openai -> openai

That case is called:

> or Railway can tell us that Google is refusing to tell them.

I'm not paying you (which let's face it, that's what an NDA is) just to find out why you messed up about as severely as one can imagine. In theory, there was a contract here: $ for cloud services, and the rug got pulled. One should get a very clear, and very apologetic explanation as to why, with no strings attached, or one should be voting with their wallet.

Now, whether Railway will do any of that, who knows.

As a sibling says, you need a "reconnect now" in the protocol. (GOAWAY, in HTTP.)

In addition to what the sibling says, if you have some sort of cordoning/graceful drain facility at the traffic level, you can also prevent the "several times" bit: bring new, patched nodes online. Disallow new connections to the outgoing nodes. Drain the outgoing nodes. Decommission them.

(I.e., only permit reconnects to patched nodes.)

  There are only three hard problems in computer science:

  1. Naming things
  2. Cache invalidation
  3. Off-by4. Multi-threading
  -one errors.