Any idea how I get myself notified once it’s up? Or a YT account to poll

Isn’t that only true though specifically at 100% CPU utilization?

If it were at 90% CPU, then you have no RAM capture, and then you can’t say anything about whether 80 or 800MB should be taken; it’s only a freebie if and only if literally no other program can do work on the machine.

I don’t see how you can map X% CPU utilization to Y% RAM capture.

Like a program could be network heavy, CPU light and mmaps a large file? Or streaming a file from disk with a constant memory allocation, but doing heavy nonstop CPU work.

The CPU / RAM capture ratio would be wildly different; the ideal for your program, while other competing programs of unknown behaviors exist, I don’t see any way for hotspot to approximate

The smarter you get about it, the closer you get to an OLAP db

Which leads to my theory… I feel like Bevy could be implemented on top of an in-memory DuckDB and get away with it

The only difficult part in arguing this is that RDBMS != SQL != RelationalAlgebra, and it’s very often forgotten

Like previously you trusted their lack of sesame based on vibes, which you probably shouldn’t have been doing, and now they’re explicitly telling you not to trust them on this; this seems to me strictly better. You’ve lost a choice that never really existed in the first place

An actually unintended consequence would be if they introduced sesame because they were going to have to put the label on it anyways

The power fantasy just needs them to die trivially. So just do that.

Except with a Result type the fact that an exception can occur and should be handled in the first place is explicit.

The problem if anything is that you MUST say something about the error case, despite the common scenario being “pass it forward” — the same reason exception do this by default. Which is also why rust for example special cases Result with the ? operator to do exactly that

SQLite/DuckDB actually enables a bunch of normally-illegal behavior when you compare to normal databases. Backups is just copy&paste of a file; spamming queries willy-nilly becomes cheap; you can version the whole DB in git (can’t diff it properly.. but you can do cross-db queries with SQLite ATTACH); locking concerns goes out the window because it’s single-writer anyways.

But if I were actively trying to support multiple users with a single source of truth, I’d probably default to Postgres. If it’s single-user, default to SQLite/DuckDB. If it’s single-user with multiple devices, default to SQLite + replication.

And then dump whatever you want, with a copy button

Or rather, you could say TFA is made more correct, by virtue of “working” not being a natural state in the first place.

But if we allow room to anthropomorphize, we can basically state that the natural goal of a natural system is to keep doing what it do, at least in regards to the larger outcomes. And for some strange reason, these systems are shockingly difficult to influence at meaningful scale in ways that are rarely true for the systems we design. In one sense, they continue to operate despite continuous minor and possibly major (but not catastrophically so, by definition) perturbations to their state

You need to burn ridiculous quantities of dino juice to influence the weather system. You need to look at windows a little funny to bring it to a complete halt. You need to bully only few substations to bring down the electrical grid.

Though cox will perpetually try to gaslight me so it doesn’t help anyways

The inherent lack of UI bloat is an added bonus.

But I think the notable aspect is not that they have recourse, it’s that the economics properly scales down. Can’t afford 20 cigarettes? An Indian shop will sell you 10. Can’t afford 10? They’ll sell you 1. Can’t afford 1? They’ll sell you half a cigarette.

Can’t afford clean water? They’ll sell you mildly dirty water. Can’t afford mildly dirty water? They’ll sell you dirty water.

Can’t afford a modern, well built, safe car? How about one with 3 wheels? No doors? No AC? 10 MPG? The crumpling structure of a tin can? An engine with less HP than a lawnmower?

In the US, there’s an arbitrary cutoff where you simply aren't allowed to be sold goods and services by anyone in normal society. It’s not about giving recourse; it’s about not actively trying to ostracize them as a separate class of humanity.

You have to actively work to stop “functional poverty” from existing. In any normal setup, it’s just more of the same economy as otherwise.

Quick random googling, I’m seeing the number 3.2% of retirees have more than $1m

https://www.investopedia.com/how-many-people-really-achieve-...

And I can’t imagine social security would become suddenly profitable by a <3% population delta