Comment by baobun 7 months ago YAML is actually not a superset of JSON.https://news.ycombinator.com/item?id=30052633 4 comments baobun Reply cluckindan 7 months ago The NO case is not valid JSON.So that leaves scientific notation. baobun 7 months ago The point is that "going right ahead and write your .yml files in JSON" is not valid. You'd have to restrict yourself to a subset of JSON to not get different semantics. joombaga 7 months ago If you configure the parser to treat it as YAML 1.2 then you don't need to restrict yourself to a subset. 1 reply →
cluckindan 7 months ago The NO case is not valid JSON.So that leaves scientific notation. baobun 7 months ago The point is that "going right ahead and write your .yml files in JSON" is not valid. You'd have to restrict yourself to a subset of JSON to not get different semantics. joombaga 7 months ago If you configure the parser to treat it as YAML 1.2 then you don't need to restrict yourself to a subset. 1 reply →
baobun 7 months ago The point is that "going right ahead and write your .yml files in JSON" is not valid. You'd have to restrict yourself to a subset of JSON to not get different semantics. joombaga 7 months ago If you configure the parser to treat it as YAML 1.2 then you don't need to restrict yourself to a subset. 1 reply →
joombaga 7 months ago If you configure the parser to treat it as YAML 1.2 then you don't need to restrict yourself to a subset. 1 reply →
The NO case is not valid JSON.
So that leaves scientific notation.
The point is that "going right ahead and write your .yml files in JSON" is not valid. You'd have to restrict yourself to a subset of JSON to not get different semantics.
If you configure the parser to treat it as YAML 1.2 then you don't need to restrict yourself to a subset.
1 reply →