Live data from Hacker News

Amazon Ion – A richly-typed, self-describing, hierarchical serialization format

amzn.github.io

1–10 of 240 posts

Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format

#5
post #3

I feel like a lot of file formats came out of companies, but even protocol buffers isn't calling itself google protocol buffers. What is it with modern companies putting their name everywhere they can?

It's funny, I didn't realize protobuf was a Google thing for a long time because of that. At least `protobuf` is a reasonably-specific search term. `ion` returns too much noise. Almost a good reason to name things weirder, like `iyon`. But then they'd get laughed at. EDIT: oh, its a Tagolog name too, and a light company.

Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format

#7
post #3

I feel like a lot of file formats came out of companies, but even protocol buffers isn't calling itself google protocol buffers. What is it with modern companies putting their name everywhere they can?

Disambiguation. There is one thing called protobufs. There are hundreds called "ion", a lot of which are more notable than an internal file format.

Edit: I was going to paste in a relevant quote from Zarf (i.e. Andrew Plotkin) on naming. Some of his most important programs have total nonsense names like "glulx", and the reasoning was that at least it would be easy to search for when the name is unique. But ironically, "Zarf" is so common a term that I can't find the quote.

Re: Amazon Ion – A richly-typed, self-describing, hierarchical serialization format

#8
post #4
post #3

I feel like a lot of file formats came out of companies, but even protocol buffers isn't calling itself google protocol buffers. What is it with modern companies putting their name everywhere they can?

Grpc?

The g is (allegedly) not for Google.
Post reply on HN