Comment on The lengths we have to go to

• TheGreenGolem@lemm.ee ⁨1⁩ ⁨year⁩ ago

  Me too, any day. I hate everything where indentation matters. Let me just throw my garbage there and YOU sort it out, you are the fucking computer, not me. You do the work.

  So fuck you, YAML! All my homies love JSON!

  source

  • KIM_JONG@lemmy.world ⁨1⁩ ⁨year⁩ ago

    All your homies hate comments.

    source

    • TheGreenGolem@lemm.ee ⁨1⁩ ⁨year⁩ ago

      My code also documents itself, of course.

      source
    • nilloc@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

      Yeah Yaml is nicer than json, but I’m not into the Python indenting at all.

      source
    • JonEFive@midwest.social ⁨1⁩ ⁨year⁩ ago

      I’m here to spread the good word about JSONC. It is the way and everyone should adopt it in place of JSON wherever possible.

      source
• wols@lemm.ee ⁨1⁩ ⁨year⁩ ago

  Yup.

  Spaces? Tabs? Don’t care, works regardless.
  Copied some code from somewhere else? No problem, 9/10 times it just works. Bonus: a smart IDE will let you quick-format the entire code to whatever style you configured at the click of a button even if it was a complete mess to begin with, as long as all the curly braces are correct.

  Also, in any decent IDE you will very rarely need to actually count curly braces, it finds the pair for you, and even lets you easily navigate between them.

  The inconsistent way that whitespace is handled across applications makes interacting with code outside your own code files incredibly finicky when your language cares so much about the layout.

  There’s an argument to be made for the simplicity of python-style indentation and for its aesthetic merits, but IMO that’s outweighed by the practical inconvenience it brings.

  source

  • merc@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    But, nobody ever copies code from Stack Overflow!

    source