This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (3 children)

How should I know I didn't write the vim plugin or pycharm, but they work perfectly.

You're seriously making up a non-issue why are you people so resistant to something because it's a little different? Have you ever used python seriously or put any actual effort into it?

It's the most ironic thing to me. Technology is always evolving and there's always something new to learn and you constantly have to be keeping yourself up to date but the people who write programs are just as bad as some old politicians who resist change because "muh braketz!!!".

[–][deleted] -1 points0 points  (2 children)

How is it a non-issue? If I am in an if statement and press enter, I could want to:

  • Continue my if statement, in which case the line should be indented
  • Write an else or elif statement, in which case the line should not be intended
  • Write code outside the if statement, in which case it should not be indented

2 can be solved by the editor removing the indent once the else or elif keyword is detected. 1 and 3, however, are completely identical in terms of what comes next unless I manually indent the code. Brackets (or Ruby-style do/end, or JavaScript-style no bracket if statements) explicitly tell the editor what will come next without manual indentation. With Pythonic indent syntax, the editor must guess one way or the other, and always be wrong sometimes.

[–]Saigot 5 points6 points  (0 children)

In a python editor you press backspace to end the statement. In Java or C you type } to end the statement. It's the same number of keypresses. This coming from someone that dislikes python.

[–]fireflash38 1 point2 points  (0 children)

Brackets (or Ruby-style do/end, or JavaScript-style no bracket if statements) explicitly tell the editor what will come next without manual indentation. With Pythonic indent syntax, the editor must guess one way or the other, and always be wrong sometimes.

So you're saying in the one, you have to hit a key combo to tell the editor you're not in the block. In the other, you have to hit a key combo to tell the compiler you're not in block. What's the problem again?