3 ms·
Thanks for your feedback. It's still an open issue, as all naming is in Rye. Currently, when I write code with it, I like the word spreadsheet, it somehow gives
by middayc 2y ago
Thanks for your feedback. It's still an open issue, as all naming is in Rye. Currently, when I write code with it, I like the word spreadsheet, it somehow gives symmetry to the two usually fat block arguments that follow. I have a lot of ideas I still want to try around spreadsheets, some might work, some not ... so I'm also not sure where the value type will "end up". That might also affect the final naming decision. Currently, spreadsheet and table are the candidates. Dataframe is too technical for what I want to do.
So far I mostly used spreadsheets as immutable data. There are cases when you want / need to change values in-place so how this would work / make sense is being explored now. In immutable data there is no reactive content, because nothing changes.
Immutable approach seems to me to be generally the default one, so maybe we won't delve too much in mutable side, but if we find it useful for specific cases (maybe more directly tied to UI) adding something like calculated columns and or rows wouldn't be hard or of of character for Rye where code and data intermingle often.
Maybe I'll just rename it to table locally and try to use it for a while to see how it feels :)
- anentropic 2y agoJust want to echo the previous commenter - I much prefer "tables" here
- andrewflnr 2y agoI want to second the idea that "spreadsheet" implies reactive data, even (or maybe especially) in a programming language context.
- middayc 2y agoWhen I went into this I was thinking we will have a concept of calculated columns and a calculated row (like option of "sums/avg/...") row at the end. Now the default mode of operation is spreadsheet as immutable data. So it's not really reactive, but it's still declarable. I am open to renaming it to "table", but I also want to first see where the mutable (spreadsheet as state holding structure) part brings me. Thanks (and also to the similar sibling comment).
- hnlmorg 2y agoI had very different expectations coming into this thread when the term “spreadsheets” was used. The term “table” is already established for this domain, for example in RDBMS. What you’re building is more inline with that verses the established definition of a spreadsheet.
- middayc 2y agoThank you for the feedback. Given all the feedback from the others, and now yours, that the word is creating wrong expectations. I am leaning toward just changing it soon and seeing from there.
- hnlmorg 2y agoAs a language author and open source maintainer myself, I do sympathise with how hard it is to name things. Keep up the good work though.
- middayc 2y agoThanks! Well, I name things and try to use them, and usually they cristalize, if not before, then through feedback of others :). I saw Murex Shell ... cool!