Fun fact: for simple text diffs, difftastic is now constrained by terminal output performance!
I halved instruction counts for diffing a 300KLOC text file against "" and I only went from 8.2 seconds to 6.5 seconds.
miniblog.
Related Posts
I'm increasingly treating terminal sessions as short lived: starting a fresh terminal tab keeps scrollback short and easy to search.
I'd love to have a terminal emulator that allows me to skip over output of specific verbose commands when searching.
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?
Are there any nice cross-platform ways to trigger a notification from a terminal?
I've been using https://pushover.net/ but you need to use a browser and it's noticeably slower than the native options.
(Pushover is great for mobile notifications though.)