Sun Jan 21 10:43:33 EST 2018

Trusted code

Thinking a lot about distributed systems and trusted code.  Ending up
with the idea that the Erlang VM cannot be the trusted base when the
remote protocol is used.

Instead, a smaller "trusted core" should be built.

I'm still finding ways to think about this.  It seems that in many
cases, architecture requirements imposed by limiting trusted code will
conflict with those imposed by functionality.

I'm in an impasse, and without breaking the loop by actually building
something, there is not going to be any progress.

Why rust?
- Types
- Memory efficient

Start with a TCP server.

OK I have an example.  Now I need a platform.  Thermostat would be the
place to start.  Needed:

- NFS boot uboot on colibri board (don't use BB for this)
- Rust cross compiler for application

NFS boot isn't really necessary, but cross compiler is.  Maybe start
by eliminating constraints that can be fixed later:

- Stick to debian on beaglebone (stretch has 1.14)
- Install native rust

EDIT: Rust is not in Debian armhf stretch.
So I need a cross compiler.