The disappointing tea.xyz
connortumbleson.com
I got a pull request from "tea.xyz" related individual and unraveled a mess of a disappointing project.

Yet another “brilliant” scheme from a cryptobro. Naturally this caused a gold-rush for scammers who outsourced random people via the gig economy to open PRs for this yml file (example)

  • umbraroze@kbin.social
    441·
    9 months ago

    Brief history of YAML:

    “Oh no! All of these configuration file formats are complicated. I want to make things simpler!”

    (Years go by)

    “…I have made things more complicated, haven’t I?”

    YAML is generally good if it’s used for what it was originally designed for (relatively short data files, e.g. configuration data). Problem is, people use it for so much more. (My personal favourite pain example: i18n stuff in Ruby on Rails. YAML language files work for small apps, but when the app grows, so does the pain.)

    • db0@lemmy.dbzer0.comOP
      281·
      9 months ago

      Ansible is using YAML and it’s orders more readable than any other config engine, like puppet or cfengine.

      • pastermil@sh.itjust.works
        3·
        9 months ago

        Ideally, yes it can be beautifully written, certainly more than bash scripts.

        With that said, I’ve also seen some hideous ansible scripts…

        • db0@lemmy.dbzer0.comOP
          11·
          9 months ago

          I work with ansible daily and this is completely wrong. You don’t do declarative syntax with scripting languages.

          It’s still the best config management precisely due to its readable syntax

    • toastal@lemmy.ml
      21·
      9 months ago

      originally designed for (relatively short data files, e.g. configuration data)

      This I can get behind. But because it’s not bad in those spaces folks think it’ll be a good idea in all spaces. Anchors do neat things, but organizing large files with YAML’s weird rules around quoting, & no support for tab indentation rub me the wrong way.