miniblog.

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:
Facebook's warning against socially-engineered XSS is neat. It's a shame it's necessary though.
Photo
Neat fact about lisp's equality functions: eq, eql, equal, equalp: the longer the name, the more values that they consider equal.
However, we shouldn't shame users for being git novices. "Always rebase/squash/amend!" is intimidating when learning branch basics. 2/2
I'm generally persuaded that "hiding the sausage making", ie rewriting history, is the best way to use git. Readable history counts. 1/2
Generally, merging single-commit PRs is much nicer without merge commits. However, I miss the PR reference when looking at history.
Announcing Refine, an interactive list editor for Emacs!
I'm giving up on "best tweets first". I like the idea in principle, but I'm just not getting much variety in my feed.
I still have yet to use EIEIO, the CLOS implementation in #Emacs lisp. I've only seen one project use it in the wild. Am I missing out?
An Ethereum soft fork, to prevent DAO money being taken, would permit a DoS: https://hackingdistributed.com/2016/06/28/ethereum-soft-fork-dos-vector/ (the system complexity here is huge)
Showing 4,366-4,380 of 7,584 posts