youtube.com/watch?v=0DLdQ6… is a really accessible introduction to programming workflows with Sly for Common Lisp.
The notion of 'stickers' is novel to me: you mark places in the code where you want to remember values (essentially tracing) or pop to a debugger (breakpoints).
"It's not possible to make a serious game in Lisp because it uses garbage collection and game programmers need raw performance to adhere to tight frame budgets."
A serious game written in Common Lisp is coming out on Steam, tomorrow. It's called Kandria.
store.steampowered.com/app/1261430/Ka…
Day 1 with neovim: holy cow this is incredibly speedy and responsive, lua's awesome
Also day 1: what's the hell is the equivalent of M-x describe-function so I can look up keybindings? M-x describe-key to go the other way?
End of day 1: slinks back to emacs
There are two different arguments for why a borrow checker isn't worth the cognitive overhead: (1) memory safety isn't worth it; (2) the performance gain from not having GC isn't worth it.
It's odd that I only ever hear (1), when (2) is to my mind the far stronger argument.
Writing code for is not very fun for its own sake. What makes it insanely addictive is the feeling upon shipping — that actual people are doing something useful with what started as a figment of your imagination. Never gets old.
Programming languages aren't sports teams: you don't have to choose one to root for!
They're more like music genres, you can enjoy more than one.
I avoid language stickers for this reason. I don't want my identity to be "I'm an X programmer".
Happy to announce my paper with Dan Licata "A Formal Logic for Formal Category Theory" has been accepted to FoSSaCS 2023. Preprint available on arxiv for now but we'll be doing some updates for the final version (arxiv.org/abs/2210.08663)
No mom it's not a "messy pile of clothes on my chair" it's an L1 cache for fast random access to my frequently used clothes in O(1) time. It needs to be big to avoid expensive cache misses (looking in my closet). I NEED to be minimizing latency, this is important to me. Please.
#GHC 9.4.4 is now available! A few good bugfixes in this release, including a fix for a rather significant performance regression. Do upgrade if you are using GHC 9.4.
Happy Holidays!
discourse.haskell.org/t/ghc-9-4-4-is…
The #GHC Steering Committee has just accepted Adam Gundry’s proposal to add custom warning categories to WARNING pragmas:
github.com/ghc-proposals/…#haskell