6 ms·

>I do not have a magical format to propose to replace it So why did you even comment in the first place?

by EC1 13y ago

p_random 13y ago
it feels like he really wanted to rant at that moment and couldn't find a better opportunity to do it.
mikeryan 13y ago
Seriously, he just lost his own argument right there.
mahmoudhossam 13y ago
He did say he uses msgpack which he claims is a step in the right direction, although it too has its issues.
garretraziel 13y ago
I don't agree with you. I think that someone can point out problem without providing the solution at the same time.
- barbs 13y ago
  He didn't just point out a problem, he actively tells people to "stop using JSON" without providing an alternative.
- HugoDias 13y ago
  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.
- jfoster 13y ago
  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.
- EC1 13y ago
  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.
rdtsc 13y ago
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.
deleted 13y ago
[deleted]

>I do not have a magical format to propose to replace it So why did you even comment in the first place?

by EC1 13y ago

>I do not have a magical format to propose to replace it So why did you even comment in the first place?

p_random 13y ago

it feels like he really wanted to rant at that moment and couldn't find a better opportunity to do it.

mikeryan 13y ago

Seriously, he just lost his own argument right there.

mahmoudhossam 13y ago

He did say he uses msgpack which he claims is a step in the right direction, although it too has its issues.

garretraziel 13y ago

I don't agree with you. I think that someone can point out problem without providing the solution at the same time.

barbs 13y ago
He didn't just point out a problem, he actively tells people to "stop using JSON" without providing an alternative.
HugoDias 13y ago
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.
jfoster 13y ago
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.
EC1 13y ago
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.

rdtsc 13y ago

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.

deleted 13y ago

[deleted]