I'm trying to figure out what to do with this thing to see if it can be tamed. I started writing.
Conversation
Replying to
But...... WOW ! Kudos! You seem to have done an impressive work! I could only grasp a first thin film of understanding by reading your markdown prose, but the goals and mission statement of exo are jaw-dropping!
1
Replying to
Thanks. Been chipping away at this after getting Erlang-infected late 2014. Currently it's still hard to separate the core ideas from all the little details that are needed to make this align. I'd like to take it out of the incubator and rebase it onto consensus reality :)
1
1
Some core ideas: 1. developer interfaces with a declarative incremental build & deployment system, 2. static types are great for isolated modules (the substrate), 3. dynamic types and late binding are necessary for always-on system evolution (the operating system).
1
Every practical always-on system has a grain boundary between early binding and late binding regimes. Pick that boundary carefully.
1
1
Replying to
1
Replying to
Just that not all dynamically/statically languages are created equal. :) I really like Erlang as the late binding part because it is pretty much also an OS, and Rust or Haskell at the other end.
1
Replying to
I designed a system between Supercollider and python (Very pattern -oriented). It's been dormant for several years but I really need to clean it, write some basic docs and put that on github. That was RRRRR I told you about :) Editing Python scores was rather nice.
1