Huh. Is was public yesterday, and still linked from their GitHub profile, but it’s dead now for me too

GitHub - modelmiser/warp-types: Session-typed GPU divergence: compile-time prevention of shuffle-from-inactive-lane bugs Session-typed GPU divergence: compile-time prevention of shuffle-from-inactive-lane bugs - modelmiser/warp-types

warp-types: session types that prevent GPU shuffle-from-inactive-lane bugs

NVIDIA deprecated a whole API because the mistake was too easy to write. This makes it inexpressible, which is the way to do it

github.com/modelmiser/warp-types

😂 yeah, a coincidence but a meaningful one. Pony seems like it takes causality seriously as a design principle rather than an afterthought. We need more of that!

Thanks! I think Pony’s reference capabilities are interesting. I’ll cover this solution space more in upcoming essays about ownership and capabilities

The Isolation Trap — Causality Erlang's mailbox design is more disciplined than Go's channels: only the owning process can read from a mailbox, and sends are asynchronous. Yet the four failure modes of shared mutable state still sh...

What happens when you build the strongest possible version of isolation?

Essay 2 in the concurrency problem series.

causality.blog/essays/the-i...

#concurrency #programming #erlang

Message Passing Is Shared Mutable State — Causality The failure of message passing to eliminate concurrency bugs wasn't surprising, it was predicted. Edward Lee argued in 2006 that the shared-memory vs. message-passing debate was a false dichotomy. Go ...

Edward Lee predicted message passing wouldn't solve concurrency. Go was the biggest real-world test, and a 2019 study of 171 bugs in Docker and Kubernetes confirmed it.

Message passing is shared mutable state. Here's why:

causality.blog/essays/messa...

#concurrency #programming #golang #plt