3 ms·

> The beauty of Python > Ritchie is whitespace sensitive As I thought. No thanks.

chm 11y ago
I also don't see the interest, but with a decent editor this shouldn't be a problem. For the little Python I write, Vim takes care of formatting the code.
- restalis 11y ago
  Wouldn't you agree that the code inspection should be easy enough to be performed without fancy tools? It's good to empower yourself with tools to make oneself more efficient but I can't see any compelling reason for us to rely on them so much that we could not do without!
duaneb 11y ago
If you're still getting stuck up on semantic whitespace in 2015, you must not use any of: + Python + Haskell + Javascript + Go + Ruby + Bash Anything else I'm missing? Whitespace is useful. Figure out how to view it in your editor and move on already. This is so far beyond bike-shedding it's just a depressing comment on how much programmers obsess on syntax.
- nostrademons 11y ago
  Swift, where semicolons are optional unless you have multiple statements on the same line. Also C++, C99, and Java if you count // comments.
- jason_s 11y ago
  ? How does Javascript use semantic whitespace?
  - omaranto 11y ago
    I'm not sure of the details but surely the answer involves semi-colon insertion.
    - Turing_Machine 11y ago
      That's the only one I'm aware of. Put me in the "if that makes a difference in your code, you're doing it wrong" camp (and yes, I recognize that not everyone agrees, and that argument has already been had too many times).
- jason_s 11y ago
  .kniht uoy naht tnatropmi erom s'ti spahrep os ytilibadaer stcapmi xatnyS
- J_Darnley 11y ago
  God no. Most of those hold no value or any interest for me. Bash only because it is the default shell. And thanks for pointing out why I should avoid the others. Have you never looked at a diff? Massive whitespace changes hide real changes. Next someone will say "Git has a -w option". To which I say "A diff without whitespace changes in those languages would be useless". I can't test it, apply it, or otherwise use it without re-indenting the source myself.
  - adrusi 11y ago
    Significant-whitespace languages don't introduce any additional whitespace changes because most people keep their code in whitespace-agnostic languages neatly indented anyway.
    - J_Darnley 11y ago
      Then I guess you don't work on any projects that only want to see non-whitespace changes.
- SamReidHughes 11y ago
  Line endings are a different question than indentation. Language design decisions do matter. "Figure out how to view it in your editor" doesn't do one lick to address the problems of semantic indentation.
girvo 11y ago
Y'know, I used to feel the same way. But using a decently configured Vim or Atom, programming in Nim (which is white-space sensitive) has been perfectly fine. Not good, not bad, it just _is_. The language itself is great, too.

chm 11y ago

I also don't see the interest, but with a decent editor this shouldn't be a problem. For the little Python I write, Vim takes care of formatting the code.

restalis 11y ago
Wouldn't you agree that the code inspection should be easy enough to be performed without fancy tools? It's good to empower yourself with tools to make oneself more efficient but I can't see any compelling reason for us to rely on them so much that we could not do without!

duaneb 11y ago

If you're still getting stuck up on semantic whitespace in 2015, you must not use any of: + Python + Haskell + Javascript + Go + Ruby + Bash Anything else I'm missing? Whitespace is useful. Figure out how to view it in your editor and move on already. This is so far beyond bike-shedding it's just a depressing comment on how much programmers obsess on syntax.

nostrademons 11y ago
Swift, where semicolons are optional unless you have multiple statements on the same line. Also C++, C99, and Java if you count // comments.
jason_s 11y ago
? How does Javascript use semantic whitespace?
- omaranto 11y ago
  I'm not sure of the details but surely the answer involves semi-colon insertion.
  - Turing_Machine 11y ago
    That's the only one I'm aware of. Put me in the "if that makes a difference in your code, you're doing it wrong" camp (and yes, I recognize that not everyone agrees, and that argument has already been had too many times).
jason_s 11y ago
.kniht uoy naht tnatropmi erom s'ti spahrep os ytilibadaer stcapmi xatnyS
J_Darnley 11y ago
God no. Most of those hold no value or any interest for me. Bash only because it is the default shell. And thanks for pointing out why I should avoid the others. Have you never looked at a diff? Massive whitespace changes hide real changes. Next someone will say "Git has a -w option". To which I say "A diff without whitespace changes in those languages would be useless". I can't test it, apply it, or otherwise use it without re-indenting the source myself.
- adrusi 11y ago
  Significant-whitespace languages don't introduce any additional whitespace changes because most people keep their code in whitespace-agnostic languages neatly indented anyway.
  - J_Darnley 11y ago
    Then I guess you don't work on any projects that only want to see non-whitespace changes.
SamReidHughes 11y ago
Line endings are a different question than indentation. Language design decisions do matter. "Figure out how to view it in your editor" doesn't do one lick to address the problems of semantic indentation.

girvo 11y ago

Y'know, I used to feel the same way. But using a decently configured Vim or Atom, programming in Nim (which is white-space sensitive) has been perfectly fine. Not good, not bad, it just _is_. The language itself is great, too.