You're right, but that's so easy to do unless the problem matters and is something that people are not easily able to realize on their own.
In this case, I'd say JSON not being the fastest it could possibly be doesn't matter too much. As a result, pointing that out isn't particularly valuable, but could be a bit more valuable if there was an easy-to-adopt solution also being proposed.
But when he said "Stop using JSON" he needs to provide a better alternative, otherwise what is the point of the complain? If he don't have a better alternative, so he should rename to "JSON sucks" or something like that.
I think he means not having something to replace in general doesn't mean not having something to replace it with in particular instances. Maybe there isn't a good general all-singing-and-dancing format.
There are language specific serializations if you never leave that language environment. There are protobufs, ASN.1, messagepack, thrift, bert, avro.
I am personally am not rushing to replace it but I can see the point he is making.
Comments
So why did you even comment in the first place?
I don't agree with you. I think that someone can point out problem without providing the solution at the same time.
He didn't just point out a problem, he actively tells people to "stop using JSON" without providing an alternative.
You're right, but that's so easy to do unless the problem matters and is something that people are not easily able to realize on their own.
In this case, I'd say JSON not being the fastest it could possibly be doesn't matter too much. As a result, pointing that out isn't particularly valuable, but could be a bit more valuable if there was an easy-to-adopt solution also being proposed.
But when he said "Stop using JSON" he needs to provide a better alternative, otherwise what is the point of the complain? If he don't have a better alternative, so he should rename to "JSON sucks" or something like that.
If you're going to post against such a widely used format, you had better have a very solid reason, and an even more solid alternative.
He did say he uses msgpack which he claims is a step in the right direction, although it too has its issues.
I think he means not having something to replace in general doesn't mean not having something to replace it with in particular instances. Maybe there isn't a good general all-singing-and-dancing format.
There are language specific serializations if you never leave that language environment. There are protobufs, ASN.1, messagepack, thrift, bert, avro.
I am personally am not rushing to replace it but I can see the point he is making.
Seriously, he just lost his own argument right there.