TIL there's a thriving Emacs community in China with its own Discourse instance! https://emacs-china.org/
miniblog.
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: https://github.com/rust-lang/rust/issues?q=is%3Aissue+label%3Arust-2-breakage-wishlist+is%3Aclosed
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! https://stackoverflow.com/a/30751992
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!)
On the benefits avoiding territorial code ownership:
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!)
I've heard nothing but good things about slime for Common Lisp. Are there any other developer tools which are so uniformly praised?
Open source, at its best, is a superb source of code reviews. Other open sourcerers are often accomplished devs with great insights.
I suspect this partly due to Emacs supporting wacky experiments, and partly because parens really benefit from good tooling.
Decades after sexpressions were invented, Emacsers are still innovating with editor tooling. E.g. lispy is genuinely novel and <3 years old.
Smalltalk's closure syntax is so lightweight that users don't feel a need for macros. Delaying evaluation (e.g. if, loops) is easy already.
Swimming with the fish: An analogy for the Smalltalk development experience: https://simberon.blogspot.co.uk/2013/01/swimming-with-fish.html
Showing 401-420 of 922 posts