Skip to content

Commit 8ef6223

Browse files
author
Steve Krouse
committed
add notes from pavel demo
1 parent 89f5ade commit 8ef6223

File tree

1 file changed

+68
-0
lines changed

1 file changed

+68
-0
lines changed

notes/paval-bazant-5-21-19.md

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: Pavel Bazant Projectional Spreadsheet Demo
3+
---
4+
5+
# Pavel Bazant Projectional Spreadsheet Demo
6+
7+
_5/21/19_
8+
9+
![Screenshot 2019-05-21 at 2 56 29 PM](https://user-images.githubusercontent.com/2288939/58102157-bddc6200-7bd8-11e9-8f19-7bc3e23a30dc.png)
10+
11+
## Notes
12+
13+
* thanks to Aria Minaei for the intro & Dan Cook for inviting Pavel to the Future of Coding Slack
14+
* excel but not based on a grid but general graph-like structure
15+
* 60% is a spreadsheet: structured document with formulas
16+
* building a tool for physicists
17+
* who should use something like spreadsheet
18+
* but instead use python for power
19+
* removing the limitations of excel that prevent me from using it to analyze data
20+
* hierarchical cell model
21+
* direct manipulation keyboard and mouse for adding and deleting cells
22+
* position of the cursor (and other data) is "reified" in document (reactive values)
23+
* can hide or show fomulas
24+
* escape hatch to svg (but maybe one day will make it inspectable)
25+
* true/false boolean that changes on clicking on it
26+
* trying to see how far he can go with this model
27+
* design principle: never use text for anything, no parsing at all
28+
* can we see you create a formula?
29+
* press = makes null formula
30+
* strings evaluate to themselves
31+
* lisp-like structured editor
32+
* what's up with the colored blocks?
33+
* they are references to specific cells
34+
* kinda a cool idea instead of hazel's numbered holes (but you can also give string names)
35+
* jupyter notebook is far from excel because the kernal is a ball of hidden state
36+
* oberserablehq is the direct solution to this
37+
* first-class links
38+
* wormhole to original thing
39+
* two most important things
40+
* everything has a uuid
41+
* links are stable when things are moved around or renamed
42+
* difference between structural and projectional editing: whether its rich data underneath or just a way to write text without syntax errors
43+
* he didn't show macros or formula networks
44+
* the system can create fragments of itself, including formulas that create formulas
45+
46+
## Questions
47+
48+
* do you have a series of benchmarks that will keep pushing forward your development?
49+
* is the goal of the project that real physicists use it? compete with jupyter notebook and python?
50+
* how are you planning to solve all the imperative things (IO Monad?)
51+
* what will the architecture be for FRP for large, complex apps, particularly with modularity in mind?
52+
* can buttons or other elements emit scoped data about themselves?
53+
* answer: going with a global approach, and have things be self-healing
54+
* you can also refer to things relatively in the tree hierarchy
55+
* how are you planning on having users learning the keyboard commands?
56+
57+
## Things it reminds me of
58+
59+
* flowsheets
60+
* pane
61+
* lamdu, isomorf, luna lang
62+
* forms/3
63+
* some eve prototypes
64+
* observablehq
65+
* original conal stuff is frp but also about the physics problem of a bouncing ball
66+
* first-class links reminds me of JE's managed copy and paste
67+
* mariano guerra's Instadeq
68+
* https://www.reddit.com/r/nosyntax

0 commit comments

Comments
 (0)