I'd like to hear your counter argument to the issues I raised, because I'm arguing it isn't going when human intervention is needed.
Json isn't friendly, which is why I put it in "readable". The trouble is you need something with clear rules, because when the human writes it wrong, they'll neet to read it under the eyes of a parser, and json is simple for that.
Well, you can write also a YAML schema. You can also write something wrong in JSON, right? And what is going to correct you is the schema. So, you can have the best of both worlds
Log in to continue
We're a place where coders share, stay up-to-date and grow their careers.
I'd like to hear your counter argument to the issues I raised, because I'm arguing it isn't going when human intervention is needed.
Json isn't friendly, which is why I put it in "readable". The trouble is you need something with clear rules, because when the human writes it wrong, they'll neet to read it under the eyes of a parser, and json is simple for that.
Well, you can write also a YAML schema. You can also write something wrong in JSON, right? And what is going to correct you is the schema. So, you can have the best of both worlds