Not really an argument on its merits.

- Matthew McConnAIhey

What I meant was, the use of the go state machine renders certain debugging techniques useless. E.g., stacktraces are less helpful, and js-debugger is pointless, since you can't guarantee the (js-debugger) will get grouped with the state you're trying to debug.

Frequently print/tap is sufficient, but core.async/go narrows your options.

He then talks about Aphyr's and Chas Emerick's similar experiences, and laments how in the earliest days, it was still possible to contribute, and how when core development closed off, it was never articulated up front until "Open Source Is Not About You", which is its own can of worms.

Overall, it's a good and nuanced discussion, but it's obvious he wasn't in unreserved love with the language, so I'm not surprised he left.

It balloons up the Js artifact, has no inherent error model, and transforms into state machine code that's hard to read/debug if something goes wrong. Plus, the `go` macro encourages overly-large functions, because it can't transform code outside its own sexpr.

As one Cognitect put it, "core.async is beautiful nonsense".

Boosting the idea that white males are discriminated against in SV: https://x.com/awesomekling/status/1874518295350837401

Defending DHH: https://xcancel.com/awesomekling/status/1971287738268909576 (DHH himself has gone full-mask-off, and wrote a whole blog post complaining that there were immigrants in London: https://web.archive.org/web/20250925050154/https://world.hey...)

Kling has been pretty quiet so far himself, but he's keeping dubious company.

You think so? I was under the impression that all the model providers have been trying to prevent use of their models to train competitor models for a while now.

> not designed for users

It's not designed for you.

I personally feel like there's no need for acknowledgement at this point, but that's just me.

I think there's a reason people are very interested in libghostty. It's a fully-featured library to build off of, but Ghostty proper still lacks a lot of polish.

What you describe sorta works, but you lose things like file/dir-based autocomplete, since your editor doesn't know about your shell session.