miniblog.

On the inefficiency of computer UIs for information display:
Emacs package of the day: emacs-rustfmt: https://github.com/fbergroth/emacs-rustfmt . Automatically formatting code on save is a revelation.
BF interpreter written in Hodor written in Rust macros: https://www.reddit.com/r/rust/comments/39wvrm/hodor_esolang_as_a_rust_macro/cs76rqk (source code is a treat to read)
Fantastic overview of the Rust compilation process, with a walkthrough of the source code:
How to design a good API for autocompletion, based on experience with YouCompleteMe:
Fascinating design rationale for Rust's crate system: allow circular dependencies but only within a project:
An entertaining Visual Studio extension ported to Emacs.
Nifty: using ud2 (the official 'undefined instruction opcode' on x86) for self-modifying code in the Linux kernel:
Interesting paper on assessing API usability based on the questions developers ask on Stack Overflow: https://www.cs.cmu.edu/~aldrich/papers/icpc15-searching.pdf
Having an interpreter and compiler allows interesting workflows. E.g elisp users can try in the interpreter then compile when they're happy.
Emacs command of the day: kmacro-name-last-macro. Concocted a great macro? Save your last macro as a named command for later use.
Achievement unlocked: created a segfault using only safe @rustlang code!
The problem with lots of small commits is they're less helpful for the reader. I try to squash rather than producing a 'twitter feed'.
I use commits on local git branch like rock climbing: they're anchor points to help you move forwards. Checkpointing work is very effective.
The new PyPI web UI: https://warehouse.python.org/ is looking really good! There's a lot of good Python out there, which deserves a good site.
Showing 4,906-4,920 of 7,549 posts