miniblog.

My 3.5yo is learning to use a mouse, and it's super interesting. He's mastered clicks and drags, but he hasn't yet figured out lifting up the mouse when run out of mouse pad. That's a tricky case where you deliberately break the relationship between mouse and cursor movement.

Trying to let my 3yo try as many different technology interfaces as possible. Mouse: not too bad, especially after reducing sensitivity. Keyboard: WASD is easy to lose track of in a sea of buttons. Controller: requires both hands together, which is tricky. Arguably the left hand is more important too, hard for a right hander.

I'm implementing an interpreter, and wondering how often I should check for interruptions (e.g. Ctrl-C). I don't want to spend too much CPU time checking whether I've been interrupted, but I also want slow programs to stop promptly. It's tricky.