Why are you commenting json that is meant for network transmission. If you are sending it over the network you are dynamically creating it. If you are dynamically creating it why don't you just comment in the language that you are using to explain what it does. The only time commenting json makes sense is when you are using it for configs. Which wouldn't matter in this case.
Well maybe that's just bad design on dockers part. Instead of autistically checking all keys why won't it just grab keys that actually relate to the job it is performing. Also I think docker has something like a description attribute for explaining what a service is/does.
>have an array / bunch of key/values >shift the last value up >UH OH YOU FORGOT TO REMOVE THE TRAILING COMMA >nlohmann JSON with comments enabled >comment out a line >UH OH YOU NEED TO REMOVE THE COMMA FOR THE LINE ABOVE
If you need comments, you are misusing JSON. It's a message passing protocol.
If you want your project to have config files, for the love of god use something easier to edit like TOML. Editing JSON by hand is bearable compared to XML but still irritating.
just use morse code with tabs as 1 and space as 0, don't use tab expansion, and install my free plugin that translates your tabs and spaces to comments.
If you need comments, you are misusing JSON. It's a message passing protocol.
If you want your project to have config files, for the love of god use something easier to edit like TOML. Editing JSON by hand is bearable compared to XML but still irritating.
The one thing about JSON that truly offends me is that it mandates UTF-8 while simultaneously using UTF-16 for its character escapes
It has worse problems but that one is just objectively shit
Makes writing an interpreter easier
{
"Comment": "This level is meant for blank",
...
}
This can't be trivially stripped out before network transmission.
Why are you commenting json that is meant for network transmission. If you are sending it over the network you are dynamically creating it. If you are dynamically creating it why don't you just comment in the language that you are using to explain what it does. The only time commenting json makes sense is when you are using it for configs. Which wouldn't matter in this case.
>docker: error: unexpected key in /etc/docker/daemon.json: "Comment"
>docker: tough breasts, refusing to start
That's not a comment.
Well maybe that's just bad design on dockers part. Instead of autistically checking all keys why won't it just grab keys that actually relate to the job it is performing. Also I think docker has something like a description attribute for explaining what a service is/does.
>his implementation doesn't support comments
pathetic
Use yaml.
Im more pissed about the unsupported trailing commas than about the comments, but that is also a major issue.
Why not drop commas entirely?
They're redundant.
http://www.relaxedjson.org/
>http://www.relaxedjson.org/
NET::ERR_CERT_COMMON_NAME_INVALID
Stopped there tbqh
>invalid cert
>every non-memelang supports trailing commas
>but not JSON
I'm so mad
Why would you ever have trailing commas tho
>have an array / bunch of key/values
>shift the last value up
>UH OH YOU FORGOT TO REMOVE THE TRAILING COMMA
>nlohmann JSON with comments enabled
>comment out a line
>UH OH YOU NEED TO REMOVE THE COMMA FOR THE LINE ABOVE
also makes diffs more noisy
Use EDN
If you need to specify comments in JSON, you are using JSON wrong.
this
just use morse code with tabs as 1 and space as 0, don't use tab expansion, and install my free plugin that translates your tabs and spaces to comments.
If you need comments, you are misusing JSON. It's a message passing protocol.
If you want your project to have config files, for the love of god use something easier to edit like TOML. Editing JSON by hand is bearable compared to XML but still irritating.
The one thing about JSON that truly offends me is that it mandates UTF-8 while simultaneously using UTF-16 for its character escapes
It has worse problems but that one is just objectively shit
what if we replaced xhtml with json? would that reduce traffic by 10% due to not having end tags
Replace with sexp and save 15%.