4 ms·

Honestly, my reason for liking spaces is "I know what every invisible character in my code is". Since I obviously cannot stop using spaces altogether, I use the

Honestly, my reason for liking spaces is "I know what every invisible character in my code is". Since I obviously cannot stop using spaces altogether, I use them everywhere. Also at work we all use 4 spaces for indentation. Nobody wants a smaller number. We have huge screens, we're not in the 80s anymore

imiric 3y ago
> We have huge screens, we're not in the 80s anymore I would like to fit more text on my modern screens, and 4-space indentation and 120+ char lines limit how many files I can view side-by-side while maintaining legibility. I still try to keep my lines around 80 chars long in 2024 for this reason.
- anthk 3y ago
  100x32 it's a sane size, but I always set 72/80 chars as a limit on messages such as Usenet/email because not everyone uses my setup.
pyrale 3y ago
> We have huge screens, we're not in the 80s anymore Unless you have huge peripheral vision too, your screen is likely not the issue.
- guenthert 3y ago
  Ha, ha. When I first sat on a (then new) 24" wide screen (I remember when 19" CRTs where huge), I actually experienced something alike vertigo. Happened never again, but I haven't tried one of those concavely curved monitors yet ...
  - inhumantsar 3y ago
    this thing in portrait mode might do the trick: https://youtu.be/CsoKWsZ-Tyw?si=LkUHiqIF429v8h6Y https://youtu.be/CsoKWsZ-Tyw?si=LkUHiqIF429v8h6Y
masklinn 3y ago
> We have huge screens, we're not in the 80s anymore Huge screens are useful to show more content e.g. multiple buffers, ancillary information (like docs). I’m not interested in wasting that additional work space in emptiness because you can’t keep to reasonable line lengths. I use 4 spaces and short lines because it naturally limits how far I can drift rightwards before I need to refactor or rethink what I’m doing. Thought I’ll readily confess that rust can be mildly annoying there: lots of things require additional blocks, and the affordances of function scope around split borrows can make extracting utility functions awkward.
user_7832 3y ago
> "I know what every invisible character in my code is" Wouldn't that be possible even when (exclusively) using tabs for indenting? Admittedly it's been a hot minute since I last programmed and I'm far more familiar with borland's ide with turbo c++ than VS code (so I don't know what the latest formatting works/features are), but if you only indent with tabs isn't that good enough? Also, do multiple spaces not take much more time to type out? Or have you remapped your tab key to multiple spaces?

imiric 3y ago

> We have huge screens, we're not in the 80s anymore I would like to fit more text on my modern screens, and 4-space indentation and 120+ char lines limit how many files I can view side-by-side while maintaining legibility. I still try to keep my lines around 80 chars long in 2024 for this reason.

anthk 3y ago
100x32 it's a sane size, but I always set 72/80 chars as a limit on messages such as Usenet/email because not everyone uses my setup.

pyrale 3y ago

> We have huge screens, we're not in the 80s anymore Unless you have huge peripheral vision too, your screen is likely not the issue.

guenthert 3y ago
Ha, ha. When I first sat on a (then new) 24" wide screen (I remember when 19" CRTs where huge), I actually experienced something alike vertigo. Happened never again, but I haven't tried one of those concavely curved monitors yet ...
- inhumantsar 3y ago
  this thing in portrait mode might do the trick: https://youtu.be/CsoKWsZ-Tyw?si=LkUHiqIF429v8h6Y https://youtu.be/CsoKWsZ-Tyw?si=LkUHiqIF429v8h6Y

masklinn 3y ago

> We have huge screens, we're not in the 80s anymore Huge screens are useful to show more content e.g. multiple buffers, ancillary information (like docs). I’m not interested in wasting that additional work space in emptiness because you can’t keep to reasonable line lengths. I use 4 spaces and short lines because it naturally limits how far I can drift rightwards before I need to refactor or rethink what I’m doing. Thought I’ll readily confess that rust can be mildly annoying there: lots of things require additional blocks, and the affordances of function scope around split borrows can make extracting utility functions awkward.

user_7832 3y ago

> "I know what every invisible character in my code is" Wouldn't that be possible even when (exclusively) using tabs for indenting? Admittedly it's been a hot minute since I last programmed and I'm far more familiar with borland's ide with turbo c++ than VS code (so I don't know what the latest formatting works/features are), but if you only indent with tabs isn't that good enough? Also, do multiple spaces not take much more time to type out? Or have you remapped your tab key to multiple spaces?