rm old notes

Author: dphilla

README.md

@@ -53,35 +53,3 @@ CMD ["/app/a.out"]
 run  `box build -f Dockerfile`
 
 This will bring in libc interaces (as imports) and create the necessary FS state, thus declaritivey creating a ready-to-run Wasm binary.
-
-### Difference in base image/layer
-
-Debian or Ubuntu or Alpine, etc. - what these things mean in a boxer context
-
-Language stacks as base image: node, ruby, python, etc.
-
-Thoughts from relay:
-
-                    //TODO: START HERE: work backward
-                    - make the compiled Wasm from marcotte with just "socket()" being executed
-
-                    - wrap (by hand) in a _start() function, compile it to wasm
-
-                    - test it, then do open() and gettimeofday(), then do all others
-
-                    - build the rest of /net calls into marcotte  -- think on https://github.com/chipmk/tcpip.js/
-                        - see: /Users/danielphillips/temp/temp/c_rust_link_example
-
-                    - get _start() wrapping into boxer cli
-
-                    - continue building out boxer cli, so that net calls can just work
-
-                    - FS, one call at a time
-
-                    // execute box
-                    const result = _start();
-                    // which:
-                    // - executes a box's start_func, which comes from entrypoint/cmd line
-                    //   - this is generated by boxer cli build, not marcotte, marcotte does everything else for system layering
-                    // - if a (/net) syscall is called, calls: r()
-                    //   - which proxies a syscall to the edge server over websocket