I've brushed up against it in the form of datalog as the query language for databases like datomic and xtdb, so it's soul is alive and well!

I'm also considering a prolog like domain specific language to make a state syncing engine with pure declarations of how the state in system A is reflected in System B, etc.

Prolog itself may not be mainstream, but it is an answer to a the universal problem space of constraint solution, so comp sci will always be in its long shadow.

I'm kind of with you here.

Lispy languages have structural editing tools that make it a lot like working directly on an AST. It's a delight when you get used to it.

The spacing/linebreaks are all just auto formatted and mostly an afterthought. It would only be one step further to present the code with the users choice of block start/end sequences.

Working with paredit was certainly one of the main ingredients for structural editing (as opposed to textual editing) to click with me. I've been watching TreeSitter with great interest.

Last Blade 2 is also a standout. Samurai Showdown 3 and 4 are nicely animated too.

I used to use a variant of this poison wine problem as an interview question. It was actually pretty good - the ones that could perceive problems abstractly usually got it without too much prompting. And the process of approaching a solution was informative.

Databricks -does- work that way, iirc.

Proctologists hate his one weird trick!

I wonder when we'll have light field capturing and emitting surfaces that would make it look like a real hole between places...

I'm independent, but I try out Gemini every time I need some dumb powershell plumbing to tie things together.

It's a net time saver, but Gemini still trips up on all of the wacky foibles of powershell, so it needs thorough code review.

I work a lot in powershell, and I want to like it. It is built around good ideas.. but oof, every time I have to special case on a return value being either a list or a single item depending on the result-len==1 or not, I die a little inside.

$alwaysList = @( Get-Something )

I think there are some tricks to ensure a list in pwsh for these sort of operations. I vaguely recall ending variable assignments with a comma to avoid this.

I've found av1 and h265 handle some things better than h264 at almost any bitrate. Usually around film grain compression.