Thanks for the quasidupe link. I didn't know about it.
This cookbook page is focused specifically on the Spreadsheet datatype, which is similar to dataframes, but also has a lot of specific ideas and views I think. It's not something that other languages couldn't implement.
Page could be a long blogpost, but since it's not temporary information, I made it in a form of a cookbook.
I am the author, but I didn't submit it here. I did submit it on lobsters, and someone reposted it to hn it seems.
Not sure if you will still see this, or if you are the right address, but anyway.
Just thinking ahead ... does this mean that for next 5 months, any subject related to Ryelang is not really desired on HN? For example, let's say that I integrate a game engine and write a post about that with examples and make a live database backend for the Rye contexts. Is this all still considered incremental releases / follow up?
No, it doesn't mean that, it's just posts that are likely to result in a generic discussion about Rye rather than the specific thing being posted are probably going to get moderated as qdupey. Hypothetical example: added some feature and posted the documentation link to it - good chance of qdupery. Blog post discussing something you implemented, a specific problem you encountered and solved (or didn't) in the process, maybe some design you are mulling - probably seen as less of a followup. Posting your stuff + some indication you're around to discuss it - typically also reduces followupness. You can also just email hn@ycombinator.com and ask the mods.
The whole thing is relatively woolly/porous, the goal is to avoid obvious repetition, not to lock you out of posting about your work on HN.
the point of "related threads" is not "this is a redundant post and should not have been made", it's more "other discussions have happened around the same general topic; if you are interested in this post you can go check out the older ones too"
https://news.ycombinator.com/item?id=26135382