8 ms·

Put me also in the group of those not feeling nim. Sad they decided to go the Python route of white space insanity.

by Tozen 5y ago

xigoi 5y ago
Have you actually worked with an indentation-based language?
- pdimitar 5y ago
  I did and hated every minute of it. Automatic formatting is fine but if you don't indent while working it can get ambiguous and format your code wrongly. Also it's harder to visually parse. So yes I did and no, your subjective tastes aren't an objective reality. What's your point?
  - xigoi 5y ago
    > if you don't indent while working it can get ambiguous And if you don't write braces in a language that uses braces, it will also get ambiguous. What's your point? > Also it's harder to visually parse. I know that ease of reading is subjective, but I still find it weird that a human finds this: a { b { c; d { e } } f } easier to parse than this: a: b: c d: e f > your subjective tastes aren't an objective reality I'm not the one who used the word "insanity" for the block delimiting system I don't like. > What's your point? You shouldn't disregard a language just for superficial syntax features.
    - pdimitar 5y ago
      > And if you don't write braces in a language that uses braces, it will also get ambiguous. What's your point? Not when they are mandatory, which they are in a number of languages (also the "do" / "end" blocks). You have no choice but to write valid code. I prefer it that way. Zero ambiguity. > a { b { c; d { e } } f } Whoever writes such code should be shot. There are newlines for a reason. And I am glad we have format-on-save these days. Less bikeshedding, exactly of the kind we're doing right now. > easier to parse than this: It's not for me, and not for one big chunk of the programmers. ¯\_(ツ)_/¯ > You shouldn't disregard a language just for superficial syntax features. Daily productivity that is taking a nose dive due to constant fight with a system my brain doesn't want to work with is not superficial. That's like trying to tighten screws with two sticks -- it can likely be made to work, but it can take a long time and will be unproductive.
      - xigoi 5y ago
        You've inspired me to create this: https://github.com/xigoi/nimdenter/ https://github.com/xigoi/nimdenter/ >Whoever writes such code should be shot. There are newlines for a reason. And I am glad we have format-on-save these days. Less bikeshedding, exactly of the kind we're doing right now. So do you use indentation or braces to read code? If the former, what are you complaining about? If the latter, why would you use a tool that adds indentation when you already have braces?
        pdimitar 5y ago
        I am not "complaining" about anything. I am expressing preferences. There were online examples where people don't indent Python code as they go and then saving the file invokes LSP's auto-format which severely botched the code logic (and it was hard to spot). Seeing one such occurrence immediately triggers my alarms: I want to write code and be productive and not squint at whether I am at the right indentation level all the time.
    - Tozen 5y ago
      I understand and respect that you may like that style, but also understand and respect that others don't. It's partially about preference. "Different strokes, for different folks". > It's not for me, and not for one big chunk of the programmers. ¯\_(ツ)_/¯ Agreed. > Daily productivity that is taking a nose dive due to constant fight with a system my brain doesn't want to work with is not superficial. Truth. That's just the reality of how a lot of folks feel about it.

Put me also in the group of those not feeling nim. Sad they decided to go the Python route of white space insanity.

by Tozen 5y ago

Put me also in the group of those not feeling nim. Sad they decided to go the Python route of white space insanity.

xigoi 5y ago

Have you actually worked with an indentation-based language?

pdimitar 5y ago
I did and hated every minute of it. Automatic formatting is fine but if you don't indent while working it can get ambiguous and format your code wrongly. Also it's harder to visually parse. So yes I did and no, your subjective tastes aren't an objective reality. What's your point?
- xigoi 5y ago
  > if you don't indent while working it can get ambiguous And if you don't write braces in a language that uses braces, it will also get ambiguous. What's your point? > Also it's harder to visually parse. I know that ease of reading is subjective, but I still find it weird that a human finds this: a { b { c; d { e } } f } easier to parse than this: a: b: c d: e f > your subjective tastes aren't an objective reality I'm not the one who used the word "insanity" for the block delimiting system I don't like. > What's your point? You shouldn't disregard a language just for superficial syntax features.
  - pdimitar 5y ago
    > And if you don't write braces in a language that uses braces, it will also get ambiguous. What's your point? Not when they are mandatory, which they are in a number of languages (also the "do" / "end" blocks). You have no choice but to write valid code. I prefer it that way. Zero ambiguity. > a { b { c; d { e } } f } Whoever writes such code should be shot. There are newlines for a reason. And I am glad we have format-on-save these days. Less bikeshedding, exactly of the kind we're doing right now. > easier to parse than this: It's not for me, and not for one big chunk of the programmers. ¯\_(ツ)_/¯ > You shouldn't disregard a language just for superficial syntax features. Daily productivity that is taking a nose dive due to constant fight with a system my brain doesn't want to work with is not superficial. That's like trying to tighten screws with two sticks -- it can likely be made to work, but it can take a long time and will be unproductive.
    - xigoi 5y ago
      You've inspired me to create this: https://github.com/xigoi/nimdenter/ https://github.com/xigoi/nimdenter/ >Whoever writes such code should be shot. There are newlines for a reason. And I am glad we have format-on-save these days. Less bikeshedding, exactly of the kind we're doing right now. So do you use indentation or braces to read code? If the former, what are you complaining about? If the latter, why would you use a tool that adds indentation when you already have braces?
      - pdimitar 5y ago
        I am not "complaining" about anything. I am expressing preferences. There were online examples where people don't indent Python code as they go and then saving the file invokes LSP's auto-format which severely botched the code logic (and it was hard to spot). Seeing one such occurrence immediately triggers my alarms: I want to write code and be productive and not squint at whether I am at the right indentation level all the time.
  - Tozen 5y ago
    I understand and respect that you may like that style, but also understand and respect that others don't. It's partially about preference. "Different strokes, for different folks". > It's not for me, and not for one big chunk of the programmers. ¯\_(ツ)_/¯ Agreed. > Daily productivity that is taking a nose dive due to constant fight with a system my brain doesn't want to work with is not superficial. Truth. That's just the reality of how a lot of folks feel about it.