Funny. When you input only milk and soy milk, it ignores the soy. If only soy, suddenly the butter needs to be vegan.

Another potential use case: This may help jujutsu auto split a large revision into small orthogonal revs.

Sometimes agent makes a monolithic commit and it's a lot of work to manually split code you didn't write. After such an auto split I can manually squash related revs into feature/ticket level.

That's a really compelling use case actually

Thx oh and maybe don't call it sem. It's not really semantic, more like a big picture view vs the ground level git lines. How about "bye", short for bird's-eye?

Literally what china is doing now

Standardization. Who writes llms.txt? Everyone writes their own? Will agents still behave the same?

Biggest design bug imo is the workers need to register for the workflows they support, but will happily pull tasks from unrelated workflows if they're on the same queue. No way to put failed tasks back into the queue again either.

Isn't split stack architectural, i.e. client heavy vs thin client. Not a hard TS feature?

With Phoenix you can write actually 0 code that runs on the client, just the backend and html templating.

I'd say cue is nicer, but the tooling available is even less mature.

"appreciation"

My phrasing was just to point out things moving in the opposite direction to what has previously been considered normal (which is also the economically intended 'normal').

Me too! I got interested in category theory and how to express a logical model of "workflows" as a category. Then ai told me workflows are a monoid and not to bother.

I note the absence of a motivation.