The real problem is the programmer mindset of “good for this purpose, good for every purpose” There so many better suited protocols out there, like avro, I don

The real problem is the programmer mindset of “good for this purpose, good for every purpose” There so many better suited protocols out there, like avro, I don’t understand the Json obsession for so many poorly suited applications. Reminds me of markdown vs anything else, I guess because github’s default readme is markdown we now have developers who don’t know anything else, like restructuredtext, “but I already know markdown, so..” .. so we see hundreds of markdown “flavors”, junktown parsers, and crazy pandoc wrapping scripts to do cross references and compile into chapters and this and that extension or tool... when the things they seek are built right into RST — just too lazy to have to learn it, or to ask our team members to have to learn it? It’s sad when we make the least effort. Think of business value, stretch your abilities to suit the needs of software design, do not limit design to what you are already comfortable with.