5 ms·

I guess it used to be more of a problem before languages started shipping their own linters and code styles (like Rust does), or agreed to use a single tool. Ki

• retrocryptid 4y ago
  Not sure I agree. As my eyesight degrades over time, I really like the idea of putting a space between a paren and a parameter in function calls / definitions. // I prefer to look at this: function example( whatever ) { : } // Instead of this: function example(whatever) { : } And I don't think it's appropriate to force everyone who uses your language to adhere to the same style. If you want to enforce a style, just encode that style in the syntax of the language. Also... my dyslexic coders tend to hate long lines of code, so we sometimes do lispy things like this: const foo = whatever( "this is a big long parameter", ( 2 + bar ) * 90, i, process.env.HOME || `/mnt/${process.env.USER}` ); instead of this: const foo = whatever( "this is a big long parameter", ( 2 + bar ) * 90, i, process.env.HOME || `/mnt/${process.env.USER`); And there's nobody's style that allows the former.
  • kutenai 4y ago
    Not quite true. Python PEP 8, kind of a core in Python style, states that lines should be no longer than 79 characters. I personally, and I believe many current Python developers use a more realistic 120 character line length.. But, in Python, long lines are frowned upon, and your multi-line function call is the preferred approach.
    • retrocryptid 4y ago
      I did not know that. I've sort of always appreciated the python community, even though python leaves me cold.