1
text editing
2
-> code editing
3
multiprocessing
4
uptime
5
self-referential
6
versioning, hot upgrades
7
network native?
8
run a node on some arch on an FPGA, connected live
9
(basically what we wanted with AVA but without the BASIC bit)
10
inspiration from E/OTP, C nodes, etc.
11
12
design a goal use first!! not just vague ideas.
13
raku has some ideas.
14
scope it to be interestingly completable (MVC) within some number of weekends.
15
16
17
we want something kind of emacs-ish, but
18
(a) not a LISP, those are boring;
19
(b) something that embraces E/OTP-like stability (and distributed-ness?);
20
(c) a nicer renderer than term-only?
21
22
smalltalk also inspires a bit.
23
24
what primitives does a text(/source?) editing language want?
25
* good (string) buffers, sensible encoding; ropes/etc. can be built from them
26
(or are 1st class).
27
* UI or the parts to make it; better to have a UI to begin with imo than try to
28
be fully generic about it.
29
30
ok, so what would using this system look like? what would we use it FOR?
31
32
are we doing work with this? are we working on comrak or a1d on this? on vyx?
33
34
---
35
36
a code editor that we can use for work that we don't have to close and reopen
37
all the time? ever?
38
39
how does this interact with version control, files on disk etc.?
40
