It is SO STUPID that spaces are widely preferred for indentation in code.

For the past, I don’t know, two hours I’ve been trying to fix YAML formatting issues that could have been fixed without any human intervention if only tabs were used. (It’s a big file, hence the duration.) (I know YAML doesn’t support tabs. That’s kind of my point.)

I even reluctantly asked Gemini (forced upon me by work; I was hoping it would change my mind in this case) why anyone would prefer spaces. It said the same irrelevant thing most people say: because some tools don’t support tabs properly.

Know what that sounds like to me? A problem with the fucking tool.

I don’t know if this is the right place to post this, but I can’t think of a better option.

  • BCsven@lemmy.ca
    link
    fedilink
    arrow-up
    3
    ·
    3 days ago

    Unfortunately its tied into the code and appa that compile those tables. And they need to support legacy customers who’ve built on top of that system. The software still opens files from that era to support aerospace customers who have a database of parts from that era.

    • thevoidzero@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      3 days ago

      Why can’t you make it work with another format, and use a flag for legacy format for those clients. Then you don’t have to deal with it as much

      • BCsven@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        I wish we could. I had hoped they’d move to CSV at least. Newer parts of the software support excel files.

        I assume Its feeding into a legacy codebase that they obviously don’t want to touch because it works and supports auto and aerospace across the globe. And many places still use data they generated in the 70s.

        The whole thing is terrible to work with, thankfully AI is great at converting simple formating to convoluted bullshit formatting.