Sometimes that’s part of the issue (or the whole deal), but sometimes it’s not even that.
Sometimes it’s that someone asked something difficult and elaborate to answer, which has been answered a ton of times, and it’s tedious to answer again and again. But if someone answers with misinformation or even straight FUD, then one needs to feel the urge to correct that to prevent misinformation.
I suffered that with questions in r/QtFramework. Tons of licensing questions, repeated over and over, from people who have not bothered to read a bit about such a well known and popular license as LGPL. Then someone who cares little for the nuance answers something heavy handed, and paints a wrong picture. Then I can’t let the question pass. I need to correct the shitty answer. :-(
JSON for serialization all the way. It’s simple and to the point. It does one thing and does it well. There’s little room for annoying surprises. Any JSON can easily be minified and prettified back and forth. If you want it in binary format you can convert it to BSON.
Yaml is too much of a feature creep. It tries to do way too many things at the same time. There are so many traps to fall into if you’re not cautious enough. The same thing can be written in multitudes of ways.
There’s a special place in hell for the inventor of semantically significant whitespace.
YAML itself is one of the circles of hell. You have to copy-paste YAML from web etc sources with dubious formatting for all eternity, and the editor doesn’t have YAML support. Also you can only use Python
Please note that AS refers to American Samoa, DC refers to the District of Columbia, FM refers to Federated States of Micronesia, GU refers to Guam, MH refers to Marshall Islands, MP refers to Northern Mariana Islands, PW refers to Palau, PR refers to Puerto Rico, and VI refers to the U.S. Virgin Islands.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.