3 ms·
To me that is the axis of discontent though. To me the badness is something like: - just want a static unconditional config -> YAML - ah but I want to pass a
by rich_sasha 4y ago
To me that is the axis of discontent though.
To me the badness is something like:
- just want a static unconditional config -> YAML
- ah but I want to pass around some variables -> YAML with some custom syntax for vars
- ah but I want conditionals based on system properties -> ...
And you end up with an awkward programming language with YAML syntax. I don’t much care if it’s XML or JSON at this stage, I just don’t want to write programs this way.
- imtringued 4y agoI am very confused by everyone abusing YAML for weird crap. For me YAML is just an alternative to writing an application.properties file (in Spring or Micronaut). Yes I do use environment variables for secrets/passwords but that is about it.
- TillE 4y agoYeah, I think 99% of the real-world usage of YAML would trivially convert to JSON. Just static data. If you need weird complex stuff, use a real scripting language like Lua or something. It should be faster than a YAML parser, at least.
- pydry 4y ago#2 onwarda means you need an API or a library or something. Unfortuntely many app creators dont recognize when their app has passed to stage #2 so we get all these unholy hacks.