I would have to disagree for similar reasons to fooker.
> It breaks copy & paste, ... not for actually communicating about code or writing tutorials.
I posted it in another respond, but my research shows retyping code can be beneficial for learning. This extends to pre-internet coding books where that was the only way to recreate the code and Zed Shaw's "Learn Python the Hard Way" [1] where he explicitly states "You must type each of these exercises in, manually. If you copy and paste, you might as well not even do them."
Airy and functional seems better for readability.
So my personal preference is strongly against airy and more like "cram what you can into one line".
But given the quick downvotes to my parent post, it seems I'm in the minority with my view that source code should be first and foremost useful.
1. With the current design standards, "beautiful code" just means lots of useless whitespace everywhere. Code should be compact and functional, not airy.
2. It breaks copy & paste, so this is really only useful for showing off, but not for actually communicating about code or writing tutorials.
3. This tool has lower contrast and lower readability than black text on a white background.
Combined, it's a tool for bragging about the wrong metric while excluding the elderly.