miniblog.

I've never seen a good design philosophy on how to sort compiler errors for the best UX. Do you order by line, or by severity? Do you put the most actionable at the end (because that's most visible when the terminal scrolls) or at the beginning?

Test code is total: we require it to always terminate or it's a failure! It also typically has 100% line and branch coverage. I feel way less nervous about refactoring tests, you can always just run them.

Ooh, difftastic is now listed on the official git website!