2 ms·
I see no reason why it can't be both, it's just that BSON happens to be a poor format for general interchange, and if you went back and redesigned you could pro
by klodolph 9y ago
I see no reason why it can't be both, it's just that BSON happens to be a poor format for general interchange, and if you went back and redesigned you could probably fix many of its flaws. I'm a little skeptical though, I would rather just throw it out.
It's kind of shitty that it was called BSON, because it falls so far short of the generality that JSON has.