miniblog.

'Knowledge archaeology':

Whilst it's usually the case that a new version of software is an overall improvement, Wikipedia edits seem to be less clear-cut.

A programming language should support any unicode symbols in programs, but only require ASCII characters that can be typed on any keyboard

"frequently unique pointers end up misused due to the overly sweet syntax". Syntax is hard!

Rather than using gensym with let, Nimrod can detect when code has side effects and can't be duplicated: http://t.co/PlX8KfRBq4 Clever.

Great collection of smalltalk and lisp demos on HN:

Learnt today that Checker (for Java) provides pluggable type systems. They've also annotated the whole JDK! Impressive.

The best looking library website I've seen in some time: http://t.co/gpCJ3scEIh

"PyBozoCrack is a depressingly effective MD5 password hash cracker with almost zero CPU/GPU load written in Python."

Centralised logging with kibana, logstash and elasticsearch is a breeze. A+ would use again.

Logstash's demo is impressive: http://t.co/HO6CIJnhGe Zero to action in four simple commands!

Python oneliner of the day: `x[:] = y` mutates x so it's the same as another list.

OH: "supporting multiple users is just a workaround for not having good virtualization technology"

The niftiest elisp hack I've seen in some time! https://github.com/wasamasa/svg-2048 http://t.co/ut3NCQjcQ1

Overall I think the emacswiki benefits from allowing editing without logging in. It reduces friction (provided you can deal with vandalism).