miniblog.

"if you partially evaluate an interpreter with respect to a particular input, you get a compiler"

Today I learnt that GHC has an incredible facility to teach it optimisations applicable to your code:

Doxygen provides an excellent highlighted view of source code with hyperlinked cross-references! https://llvm.org/docs/doxygen/html/DataLayout_8cpp_source.html Why is this rare?

Maybe flat comments are better than nested. In HN the top tree dominates. In mailman there's next/prev links but a tree isn't linear!

@thattommyhall looks like bpython to me.

I've added GIFs to the smartparens README! https://github.com/Fuco1/smartparens#smartparens It can really help new users grok the feature set.

I learnt today that Rust's cargo has a clean command. Neat! I've been rm -rf'ing the target directory all this time.

JavaScript surprise of the day: [2] * 3 == 6.

If twitter can be microblogging, then GIFs are mico screencasts. They're a brilliant way of showcasing Emacs packages (working on some now).

Emacs tip: if you have a great keyboard macro, but always do the same thing after, you can extend it. C-u F3.

I'm often surprised by the effectiveness of a good README. It brings huge clarity and steers development. It may be GitHub's best feature.

Skimming the docs for lens.js: https://www.npmjs.com/package/safety-lens makes lenses look rather like lisp's setf to me. Is this superficial or deep?

It is so difficult to mix a good REPL (late binding everywhere!) with an optimising compiler (inlining etc). Do any langs do this well?

The remarkable success of Go, despite all the critiques, make me curious enough to try it. I suspect the tooling quality wins users over.

I'm considering using my own builds of Emacs simply because the links to C source code work. I wish distro packages had this.