miniblog.

Neat idea in LLVM: adding a pass to ensure that generated code actually respects the requested calling convention:

Twitter will stop counting links and pictures towards the 140 char limit! https://www.bloomberg.com/news/articles/2016-05-16/twitter-to-stop-counting-photos-and-links-in-140-character-limit A positive step I think.

There is so much work on polishing Rust docs that there's a weekly newsletter! https://guillaumegomez.github.io/this-week-in-rust-docs/blog/this-week-in-rust-docs-4 This level of polish is so rare.

There's something really neat about defining let in terms of lambda in Scheme. The language is both tiny and potent.

Great post discussing the weaknesses of literate programming:

Rust's crater is also neat. Here's an example of fixing a compiler issue and rebuilding public packages to test it.

Rust tests every PR against a very impressive range of platforms. No code gets merged if any fail!

I'm also still getting used to Smalltalk-style docstrings. They're 1st person, so eg Set "I represent a set of objects without duplicates".

"Forget it -- do nothing -- sorry I asked". The Pharo IDE has attitude!

The success of microblogs (Twitter, Weibo) and micro vlogs (Vine) is in some ways a vindication of the pomodoro technique. Small is easy.

The excellent, new Emacs website is live!

Delightful blog post showing CLOS (the powerful OO system in Common Lisp): https://eli.thegreenplace.net/2016/a-polyglots-guide-to-multiple-dispatch-part-3/ (eg value dispatch is cool, as is :after)

Playing with Dr Racket today. It has some really cute highlighting for stack traces and symbol definitions.

Pharo takes a really interesting approach to recursion: instead of TCO, it just has an unbounded stack! '10000 factorial' just works.

I find subversion-based projects difficult to contribute to. With git pull requests and CI, I know everything is in good order when I merge.