3 ms·

> When I work on a codebase with formatting standards I try to follow them. This is 2013, though, and when I work on my own stuff I format it to get the most re

> When I work on a codebase with formatting standards I try to follow them. This is 2013, though, and when I work on my own stuff I format it to get the most readability on my Macbook or 32" 1080p desktop screen, not a VT100 from 1987. And then someone working on your code on an eeePC will have a great time!

ratsbane 14y ago
If you're doing a lot of development on an eeePC then line length may not be your biggest obstacle.
- jimktrains2 14y ago
  Who are you to choose when and how I code. eeePCs work well in commuting situations.
  - tomsthumb 14y ago
    Visual Studio 2010 ain't quite zippy on a netbook. They are fantastic, but they do have notable limits.
    - jimktrains2 14y ago
      Sure, but I dev in vim, linux, and the associated compiler/interpreter. A netbook is quite a handy for that type of dev.
cabirum 14y ago
The options are: use smaller font size, enable word-wrap, buy a higher-resolution display (or two), use your IDE to auto-format code according to your preferences. I don't really see anybody using eeeePC for serious coding in 2013.
- jimktrains2 14y ago
  > use smaller font size Makes the code harder to read > enable word-wrap Makes the code harder to read > buy a higher-resolution display Increases cost and I can't take an external on the subway/train. > use your IDE to auto-format code according to your preferences So, make it 80 to 120 chars per line myself > I don't really see anybody using eeeePC for serious coding in 2013. Because the year means sooooo much. Who are you to choose when and how I code.
  - cabirum 14y ago
    > Who are you to choose when and how I code I'm asking the same question when 80 chars limit is enforced on me.
    - jimktrains2 14y ago
      80 to 120 char has other advantages over just screen size. It's easier to read as well. Working on a team is giving and taking of everyone's capabilities. I've had to work on teams that use odd tabbing, but I do it because that's what others use.

ratsbane 14y ago

If you're doing a lot of development on an eeePC then line length may not be your biggest obstacle.

jimktrains2 14y ago
Who are you to choose when and how I code. eeePCs work well in commuting situations.
- tomsthumb 14y ago
  Visual Studio 2010 ain't quite zippy on a netbook. They are fantastic, but they do have notable limits.
  - jimktrains2 14y ago
    Sure, but I dev in vim, linux, and the associated compiler/interpreter. A netbook is quite a handy for that type of dev.

cabirum 14y ago

The options are: use smaller font size, enable word-wrap, buy a higher-resolution display (or two), use your IDE to auto-format code according to your preferences. I don't really see anybody using eeeePC for serious coding in 2013.

jimktrains2 14y ago
> use smaller font size Makes the code harder to read > enable word-wrap Makes the code harder to read > buy a higher-resolution display Increases cost and I can't take an external on the subway/train. > use your IDE to auto-format code according to your preferences So, make it 80 to 120 chars per line myself > I don't really see anybody using eeeePC for serious coding in 2013. Because the year means sooooo much. Who are you to choose when and how I code.
- cabirum 14y ago
  > Who are you to choose when and how I code I'm asking the same question when 80 chars limit is enforced on me.
  - jimktrains2 14y ago
    80 to 120 char has other advantages over just screen size. It's easier to read as well. Working on a team is giving and taking of everyone's capabilities. I've had to work on teams that use odd tabbing, but I do it because that's what others use.