Comment by baobun 5 days ago YAML is actually not a superset of JSON.https://news.ycombinator.com/item?id=30052633 4 comments baobun Reply cluckindan 5 days ago The NO case is not valid JSON.So that leaves scientific notation. baobun 5 days 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 5 days 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 5 days ago The NO case is not valid JSON.So that leaves scientific notation. baobun 5 days 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 5 days 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 5 days 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 5 days 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 5 days 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 →