51–60 of 73 posts
Why do all these serialization frameworks like protobufs, flatbuffers, capnproto, etc. have bespoke schema languages? Why not just use JSON-based schema so that you don't need custom parsers for it? It would definitely make metaprogramming easier as well.
Why do all these serialization frameworks like protobufs, flatbuffers, capnproto, etc. have bespoke schema languages? Why not just use JSON-based schema so that you don't need custom parsers for it? It would definitely make metaprogramming easier as well.
Because JSON-based schemas are excessively verbose making them painful to read and write, to the point where really nobody wants to do so. Consider: struct Person { name @0 :Text; age @1 :UInt16; } vs.: "declarations": [ { "name": "Person", "kind": "struct", "fields": [ { "name": "name", "type": "text", "ordinal": 0 }, { "name": "age", "type": "uint16", "ordinal": 1 } ] } ]
Earlier quoted context omitted.
> ... allow you to specify that an input string/blob should be smaller than 10MB and refuse to deserialize it if it is longer ... why ? are there no cases where serializing even larger file is valid ?
sure, a lot of cases, I suspect that S3 upload limits are different from imgur.
mechanism vs policy and all that.
>Cap’n Proto unions are not first class types. Instead, they are fields of structs In some binary data description format, I didn't include unions because they are just a special case of what I called "conditional sequences". But then I added them, because it is very difficult or impossible to figure out whether a set of conditional sequences corresponds to a union (all must have same size, which is only known at enc…
Earlier quoted context omitted.
yes ?
Knowing that it's from a few years ago gives helpful information to the potential reader. 1) Someone may have read the essay before, remembered the point, but forgotten the exact title. It has, after all, been posted on HN twice before. Simply reading the comment that it's from 4 years ago may be enough to confirm that it's the same article, as it did with me. While the essay has the date right at the top, in general…
Honestly I didn't expect my original comment to be controversial.
Earlier quoted context omitted.
Knowing that it's from a few years ago gives helpful information to the potential reader. 1) Someone may have read the essay before, remembered the point, but forgotten the exact title. It has, after all, been posted on HN twice before. Simply reading the comment that it's from 4 years ago may be enough to confirm that it's the same article, as it did with me. While the essay has the date right at the top, in general…
The submission guidelines contain no such allowance. They specify a very limited set of cases where the title of a submission can be modified from the web page title.
Earlier quoted context omitted.
The submission guidelines contain no such allowance. They specify a very limited set of cases where the title of a submission can be modified from the web page title.
Thanks. I wasn't aware that putting a date in the title might violate the guidelines.
You can see dang, one of the moderators, write: "It's the convention on HN to add the year to a title when the article isn't from this year." at https://news.ycombinator.com/item?id=27867435 ,
write "On HN, it's the convention to add the year when a story is more than a year and a bit old." at https://news.ycombinator.com/item?id=16306830
and write "It's just the convention to add the year in parens (and for commenters to mention when we missed one)." at https://news.ycombinator.com/item?id=8244765 .
Found via https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... .
If orhmeh09 has issue with how to interpret the submission guidelines, I suggest contacting hn@ycombinator.com to resolve the issue.
Earlier quoted context omitted.
sure, a lot of cases, I suspect that S3 upload limits are different from imgur.
and feel free to do that in _your_ application. don’t shackle others with the limitations of your domain. mechanism vs policy and all that.
Earlier quoted context omitted.
It's common on HN to note the date for reposts. The mods will usually add the year to the title if it's not included. So that's probably all that CoastalCoder was signaling.
Users are not advised to do this themselves. The submission guidelines contain no such allowance. They specify a very limited set of cases where the title of a submission can be modified from the web page title.
See dang, one of the moderators, affirm this multiple times at https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... , most recently 17 days ago.
Why do all these serialization frameworks like protobufs, flatbuffers, capnproto, etc. have bespoke schema languages? Why not just use JSON-based schema so that you don't need custom parsers for it? It would definitely make metaprogramming easier as well.
Avro uses json for its schema language.
Avro schema in Json is very unreadable in my experience.
Another bad thing is something like ["int", "null"] gets formatted over 2 lines by standard JSON formatters, making it even harder to read.