Post 9v6mDtrayv8leGFjCS by debugninja@banana.dog
 (DIR) More posts by debugninja@banana.dog
 (DIR) Post #9v5WX3vtyVXvxJQFjU by debugninja@banana.dog
       2020-05-16T01:00:16Z
       
       0 likes, 0 repeats
       
       #FuckItFridayYAML is actually good and in some cases better than JSON....come at me!
       
 (DIR) Post #9v5We2kskh0qKWb4Ai by neauoire@merveilles.town
       2020-05-16T01:01:30Z
       
       0 likes, 0 repeats
       
       @debugninja I agree 🙋
       
 (DIR) Post #9v5XXaIbjolCI9r7FQ by cancel@merveilles.town
       2020-05-16T01:04:41Z
       
       0 likes, 0 repeats
       
       @neauoire @debugninja YAML is extremely bad. nothing about it is good.
       
 (DIR) Post #9v5XXaSX8uhSmwV2ie by debugninja@banana.dog
       2020-05-16T01:11:30Z
       
       0 likes, 0 repeats
       
       @cancel @neauoireAgree to disagree!YAML is a superior configuration file format and does a great job at capturing hierarchical info but it's not as good as a data transfer / storage format.  I think most people's complaints for yaml have to do with using it as a marshaling / serialization format.I mean people love JSON but as a human readable configuration file format it can't even take comments.TOML is better than JSON and YAML for config though but I don't have room in my heart for yet another format when YAML gets it done.
       
 (DIR) Post #9v5XeaqI7HZy0Ix90K by cancel@merveilles.town
       2020-05-16T01:12:43Z
       
       0 likes, 0 repeats
       
       @debugninja @neauoire I just usefoo=barUnless it needs to be more complicated, then I use a scripting language or something. the "rich" configuration stuff is a nightmare, you just end up with a bad turing equivalent language.
       
 (DIR) Post #9v5Yh3JBLr2gp5Cdou by montagsoup@aleph.land
       2020-05-16T01:24:21Z
       
       0 likes, 0 repeats
       
       @debugninja There are some things I really don't like about YAML. I think it's way to complicated which makes it harder to write parsers for, increases the attack surface of your parser, and makes it harder to remember. I shouldn't have to consult language documentation for a configuration language, especially since the amount of time I'm in contact with it will usually be short.I also don't personally like how a single tab character can invalidate a whole file. It really threw me for a curve the first time I came across it, especially since I didn't realize I was editing a YAML file (all I knew was it was a config file I wanted to edit).Just my opinion though, you can like it if you want.
       
 (DIR) Post #9v5YnmM6mQ9oGumMm8 by chipmonk@metalhead.club
       2020-05-16T01:25:33Z
       
       0 likes, 1 repeats
       
       @debugninja I see your YAML and raise with bencoding and a hexeditor.
       
 (DIR) Post #9v5x7o3SZO7EEX8gU4 by neauoire@merveilles.town
       2020-05-16T01:15:23Z
       
       0 likes, 0 repeats
       
       @cancel @debugninja I use a subset of YAML for everything I do as it's a lot more readable than JSON. It's basically no contest for me, I couldn't imagine using all these extra {"\"} just to define hierarchy, no way.
       
 (DIR) Post #9v62jVUQXfTlQiY6sa by zacanger@mastodon.social
       2020-05-16T07:00:12Z
       
       0 likes, 1 repeats
       
       @debugninja yaml is good and more readable than json, i agree, but it also has way too much stuff in it that should never have been added IMO, like... why is there a base64 type, for example
       
 (DIR) Post #9v6hopsGHEACDgMClU by charims@mastodon.technology
       2020-05-16T14:41:22Z
       
       0 likes, 0 repeats
       
       @debugninja I really like yaml. If you aren't trying to use every single one of its features at the same time, its incredibly readable and understandable.  Its good to have user-readable/writeable configs, and you need an editor which converts tabs to spaces. I have worked with ansible for about 6 years, all in yaml. There are some best practices when writing yaml that many people miss, but its not hard to fix.To exchange data between services, json I think is better suited.
       
 (DIR) Post #9v6lFpizEzWDR9aGlE by zenhob@butts.team
       2020-05-16T15:19:51Z
       
       0 likes, 0 repeats
       
       @debugninja yaml has comments which makes it better for config files imo
       
 (DIR) Post #9v6mAgQ4Vdsj5GqRAe by charims@mastodon.technology
       2020-05-16T14:43:15Z
       
       0 likes, 0 repeats
       
       @debugninja anyways, just from a pure markup language standpoint, yaml is much more readable and maintainable than XML IMO. The yaml structure has less syntax, is more readable, and forces readability by its very nature.
       
 (DIR) Post #9v6mDtrayv8leGFjCS by debugninja@banana.dog
       2020-05-16T15:30:30Z
       
       0 likes, 0 repeats
       
       @charims Basically I agree 100% :amigacheck:
       
 (DIR) Post #9v7IBEA6FkVcGdg3mq by mathew@mastodon.social
       2020-05-16T21:28:50Z
       
       0 likes, 0 repeats
       
       @debugninja https://noyaml.comI'd even take XML over YAML.
       
 (DIR) Post #9v8iaDLpCGZyxThGXg by debugninja@banana.dog
       2020-05-17T13:59:22Z
       
       0 likes, 0 repeats
       
       @mathew look I know people can be overly dramatic on the internet but advocating for xml, even as a joke, is not cool :p