3 ms·

Cool project, but the title is a bit confusing: > "A code editor that feels like a spreadsheet" It literally is a spreadsheet though right? Is there something

by gitgud 7y ago

Cool project, but the title is a bit confusing: > "A code editor that feels like a spreadsheet" It literally is a spreadsheet though right? Is there something that separates this from an google sheet? Also, the source repository on [1] Github is a bit more informative (for this audience). [1] https://github.com/chrispsn/mesh https://github.com/chrispsn/mesh

raidicy 7y ago
AFAIK this is not the repo for the code in the talk. The talk is about using K as a language. The repo in [1] is a JS implementation that runs in the browser. It seems like it's his first run at this idea of spreadsheets accompanying code.
chrispsn 7y ago
Users have strong expectations about what features a "spreadsheet" application should have, so I say it merely "feels like" a spreadsheet to help manage those expectations. For example, in existing spreadsheet programs, each cell gets an A1-style location reference (even in an Excel table or a dynamic array). That's not the case in Mesh, but it does something similar: a cell's default name is where it was entered in the grid UI, and (soon!) we update that name when the cell gets moved around.
- gitgud 7y ago
  > That's not the case in Mesh, but it does something similar: a cell's default name is where it was entered in the grid UI, and (soon!) we update that name when the cell gets moved around. But that's still possible in Excel too right? With "named ranges". Anyway, I see you're the creator and want to thank you for sharing the project and releasing the source-code. I feel like it's pushing the boundaries, but it can't really be explained yet. Look forward to seeing future development in this!
  - chrispsn 7y ago
    Kind of - in Excel everything just has a location reference, even if you name it. So that means you can get collision errors if a dynamic array expands into another cell.

by gitgud 7y ago

raidicy 7y ago

AFAIK this is not the repo for the code in the talk. The talk is about using K as a language. The repo in [1] is a JS implementation that runs in the browser. It seems like it's his first run at this idea of spreadsheets accompanying code.

chrispsn 7y ago

Users have strong expectations about what features a "spreadsheet" application should have, so I say it merely "feels like" a spreadsheet to help manage those expectations. For example, in existing spreadsheet programs, each cell gets an A1-style location reference (even in an Excel table or a dynamic array). That's not the case in Mesh, but it does something similar: a cell's default name is where it was entered in the grid UI, and (soon!) we update that name when the cell gets moved around.

gitgud 7y ago
> That's not the case in Mesh, but it does something similar: a cell's default name is where it was entered in the grid UI, and (soon!) we update that name when the cell gets moved around. But that's still possible in Excel too right? With "named ranges". Anyway, I see you're the creator and want to thank you for sharing the project and releasing the source-code. I feel like it's pushing the boundaries, but it can't really be explained yet. Look forward to seeing future development in this!
- chrispsn 7y ago
  Kind of - in Excel everything just has a location reference, even if you name it. So that means you can get collision errors if a dynamic array expands into another cell.