-
-
AppSignal
AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
-
> This might be the core contention. I don't know if using actual capabilities in a language would have problematically bad ergonomics. You'd probably be passing more arguments to functions. But haskell seems to manage ok despite needing to pass IO to functions that need it. Capabilities seem similarly inconvenient. I think I'd need to see it tried. I agree - I might need to try it myself.
You can try it now yourself in Haskell! This is my effect system, based on capabilities: https://hackage.haskell.org/package/bluefin
One of the common objections I hear to Bluefin is "isn't it too inconvenient to pass around capabilities everywhere?". Perhaps surprisingly, no, I haven't found it remotely inconvenient. I find it liberating, actually.
Related posts
-
What mathematicians should know about the Lean Theorem Prover: reliability & AI
-
Show HN: Llmll – AI agents fill typed holes, an SMT solver rejects wrong fills
-
RacketCon Is Saturday
-
Show HN: Lask – A task runner with a type system and pinned Docker environments
-
Differences Between `Foldl` and `Foldr`