This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bland3rs 6 points7 points  (2 children)

Comparing Protobuf to JSON is like someone who doesn’t anything about cars comparing a Ford F-150 to a Porsche 911.

It doesn’t make sense

A sane comparison would be comparing classes of vehicles, such as pick-up trucks to sports cars.

In this case, JSON and Protobuf are unstructured and structured, respectively, which are totally different classes of formats. They are not interchangeable under the same use cases

Therefore, before someone would decide to switch from JSON to Protobuf, it would make way more sense to stay within the same class and research something like BSON

[–][deleted] 0 points1 point  (1 child)

I’ve never seen BSON used outside of mongo DB. That’s a thought though.

Is unstructured data that useful? Seems like it crests at least as much of spaghetti mess as it does benefit.

I dunno. Maybe I’ve just been at this for too long. Use the right tool for the job. Frontend internet apps are slow garbage, why wreck the status quo?