3 ms·
Because one takes an extra line. For something that's effectively an error condition. There's so reason errors should take up so much vertical code space (which
by __david__ 10y ago
Because one takes an extra line. For something that's effectively an error condition. There's so reason errors should take up so much vertical code space (which is at a premium even today, given how wide monitors are). This is one of my primary quibbles with golang, and why I will never give in to the community's slavish devotion to "go fmt @
- nitrogen 10y agoTry rotating your screen 90 degrees.
- chris_wot 10y agoDo you know how weird that makes me look when I'm coding on my laptop at the airport?
- nitrogen 10y agoNo doubt it's quite weird, but I am of the opinion that hardware should serve the code and coder, not the other way around. Maybe use a portrait orientation tablet with a bt keyboard for travel. I think there could be a small market for laptops with a portrait mode, too.
- echlebek 10y agoYikes. Do you realize how useful it is to have a single consistent formatting for source code? It eliminates an entire class of arguments. Or do you enjoy arguing about tabs and spaces, and when to make newlines?