As a developer, you develop an intuition for the computational cost of doing things. It's possible to become computationally stingy: "a real time text editor (i.e. updates as soon as you type) is a huge waste of resources!"
I wish I had a good name for this phenomenon.
miniblog.
Related Posts
nREPL is a really interesting protocol for developer tools. It's extensible, but one of the basic operations is eval().
If your nREPL server doesn't support a given operation, you can just send an eval request to achieve the same result!
Really elegant developer tool: Go's inline IDE feature is used with deprecation markers, so call sites are autofixed from OldApi() to NewApi() based on the implementation of OldApi.
Are there any developer experience advantages for `x := 1` over `let x = 1`?
A `let` keyword probably improves parsing error behaviour, and makes declarations more visible.
:= is more concise though.