Knit, Chisel, Hack: Building Programs in Guile Scheme https://www.youtube.com/watch?v=TVO8WXFYDIA (great overview of the Guile design from @andywingo himself!)
miniblog.
TIL there's a thriving Emacs community in China with its own Discourse instance!
Writing tests in the traditional red-green approach is invaluable. But make sure they're red for the right reason!</just-lost-10-minutes>
.@melpa_emacs looks like badges are broken? E.g. https://stable.melpa.org/packages/loop-badge.svg -- seems to be an issue on @Shields_io (cc @sanityinc)
Whilst there are no plans for a Rust 2.0, there is an interesting list of desirable breaking changes:
Great blog post comparing macros in Racket and Haskell: https://blog.ezyang.com/2016/07/what-template-haskell-gets-wrong-and-racket-gets-right/ (we need more polyglot macro comparisons—cross pollination!)
I'm a huge fan of writing READMEs, and I hold GitHub entirely responsible :). The need for docs varies, but everything needs an overview.
I'm also reading claims that prompts are *much* faster than full continuations!
I'm really interested to see that Guile is moving away from call/cc to prompts. A discussion of motivations: https://wingolog.org/pub/qc-2012-delimited-continuations-slides.pdf [PDF]
Debugging Emacs memory leaks: https://notes.secretsauce.net/notes/2015/09/19_debugging-gnu-emacs-memory-leaks-part-1.html (reproduction, measurement and bisection!)
Inter-Procedural Optimization and Derefinement https://www.playingwithpointers.com/ipo-and-derefinement.html (excellent post showing how combining optimzns can cause surprises)
The Renewed Case for RISC: Avoiding ISA Bloat with Macro-Op Fusion for RISC-V https://arxiv.org/abs/1607.02318 (enjoyable and quantitative!)
I've had a personal disk start giving random fsck errors. Periodic reminder to back up your data!
TIL Fortran has a keyword PURE that allows you specify if code has side-effects: https://stackoverflow.com/a/30315370/509706 (effect-based languages are rare!)
Showing 4,351-4,365 of 7,584 posts


