4 ms·

How useless. 1. With the current design standards, "beautiful code" just means lots of useless whitespace everywhere. Code should be compact and functional, no

How useless. 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.

fooker 7y ago
>Code should be compact and functional, not airy. Airy and functional seems better for readability.
- fxtentacle 7y ago
  If I had to choose between 2 screens full of source code with lots of whitespace, or half of a screen condensed, I'd always choose the variant that fits on my screen. 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.
  - touktouk 7y ago
    It is quite possible that people agree with you that source code should be first and foremost useful, but disagree on compactness vs airiness.
  - fooker 7y ago
    >cram what you can into one line This is how code gets thrown away and rewritten. Fixing bugs in dense code is a nightmare, if the code was written by someone else.
tsumnia 7y ago
> Code should be compact and functional, not airy. 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." [1] https://learnpythonthehardway.org/python3/intro.html https://learnpythonthehardway.org/python3/intro.html

fooker 7y ago

>Code should be compact and functional, not airy. Airy and functional seems better for readability.

fxtentacle 7y ago
If I had to choose between 2 screens full of source code with lots of whitespace, or half of a screen condensed, I'd always choose the variant that fits on my screen. 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.
- touktouk 7y ago
  It is quite possible that people agree with you that source code should be first and foremost useful, but disagree on compactness vs airiness.
- fooker 7y ago
  >cram what you can into one line This is how code gets thrown away and rewritten. Fixing bugs in dense code is a nightmare, if the code was written by someone else.

tsumnia 7y ago

> Code should be compact and functional, not airy. 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." [1] https://learnpythonthehardway.org/python3/intro.html https://learnpythonthehardway.org/python3/intro.html