This was my first thought as well.

The newer parts aren't all that bad. It's taken a while for us to catch up with other cities with properly functioning trains, for example...

You make deliberate and subtle errors so you can detect later plagiarism more easily.

I wonder whether swimmers benefit from this, after all, they're breathing-constrained (if going at anything more than a comfortable pace).

I use it on Linux and think it's great. My laptop has a screen with some crazy-high DPI and a monitor which doesn't. Changing the font sizes in settings to suit has never left me with a poorly rendered view.

The Shockwave Rider is brilliant, and the savant hero reflected in many subsequent works. Neo, anyone?

Amen. Even with those 5k word monsters it's brutally hard. Andreas Fertig's cpp-insights is really helpful, when is able to complete the coroutine transform.

FWIW, I think a useful addition would be for compilers to output the intermediate source code, so you can reason more easily about behaviour and debug into readable code.

I don't find this surprising at all. Humans are tool-users, and valuing an object's utility and experiencing a feeling of something like loss when it's neglected or loses efficacy would seem to be an advantageous trait.

Username matches the current URL

It's entirely possible, have done it at few times. For example, the `fby` verb[?] annoyed me one too many times, so I pulled it apart to see what was going on. In contrast to json.k it's quite short. I usually split each separable idea into a new line and introduce a bunch of new variables to track state that would otherwise be passed from right to left. Lengthy end-of-line comments are my chosen way of understanding q or k when I come back to anything later.