Maybe another comment has mentioned this, but you might like StrictYAML. It is a subset of YAML designed specifically to weed out all ambiguity. It might even be the solution you want to suggest as an alternative to YAML.
I can understand where you're coming from with Bash and PowerShell. Learning by mistakes was painful and very confusing in Bash, and I honestly think shell languages need a complete redesign. Funny enough is I actually made an experimental shell to address this by having it accept all arguments in the form of YAML to reduce ambiguity.
I love YAML, but I don't want to pretend that it doesn't have serious flaws. Which is why I mention the problems that it has. I really want it to completely replace JSON, but it is going to need improvements before that is realistic.
For me personally, if it is humans writing YAML with syntax highlighting enabled, I think YAML is the gold standard for config files.
Hi i am working on the StackStorm open source project to automate some dev opsy things and the workflows are built in YAML. It is himan readable but brittle. But have been wondering if its the best way to define workflows which may be more dynamic and can be better expressed differnetly, such as ith bitwise operators.
So am interested in alternatives without throwing out the baby wih the bathwater. So curious about strictYAML.
But since a workflow ideally has programmability and graph attributes, what other alts are there?
I don't have vast experience with different alternatives. I think one of the big challenges often faced is you want something readily available in multiple languages.
I really like Lua. Not as a programming language, but the lightweight embedded part. They keeped the syntax light, but don't go overboard like yaml.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yaml advertising itself as human friendly, then having the same complexity as bash... Bash and powershell don't do that.
It is interesting that you list problems with yaml others are saying it does well... Hmmm...
Maybe another comment has mentioned this, but you might like StrictYAML. It is a subset of YAML designed specifically to weed out all ambiguity. It might even be the solution you want to suggest as an alternative to YAML.
I can understand where you're coming from with Bash and PowerShell. Learning by mistakes was painful and very confusing in Bash, and I honestly think shell languages need a complete redesign. Funny enough is I actually made an experimental shell to address this by having it accept all arguments in the form of YAML to reduce ambiguity.
I love YAML, but I don't want to pretend that it doesn't have serious flaws. Which is why I mention the problems that it has. I really want it to completely replace JSON, but it is going to need improvements before that is realistic.
For me personally, if it is humans writing YAML with syntax highlighting enabled, I think YAML is the gold standard for config files.
Hi i am working on the StackStorm open source project to automate some dev opsy things and the workflows are built in YAML. It is himan readable but brittle. But have been wondering if its the best way to define workflows which may be more dynamic and can be better expressed differnetly, such as ith bitwise operators.
So am interested in alternatives without throwing out the baby wih the bathwater. So curious about strictYAML.
But since a workflow ideally has programmability and graph attributes, what other alts are there?
I don't have vast experience with different alternatives. I think one of the big challenges often faced is you want something readily available in multiple languages.
I really like Lua. Not as a programming language, but the lightweight embedded part. They keeped the syntax light, but don't go overboard like yaml.