Steve you're a good chap doing some solid, respectable and valuable work. These things are just troglodytes looking to inflict pain. The interesting thing is, they could totally transform themselves by doing constructive work and presenting it to the community. It's then, quite possibly, they realize, it is your attention they seek.
a) yes it will, we'll have to do some design on the `fvm` to make it hotswap. It won't be ready for this stabilization release. The functionality is already there it just needs
b) I'm not really focusing on other market occupants. We need this system to solve some pretty hairy problems 100TB problems.
c) 'feature-credible, testable release' primarily this is dependent on `nixcrates`, documentation and maybe getting a few more services examples. I'd say a couple of weeks.
An author here: we're working on the nixcrates project to remove cargo and allow for closer integration between nix and crates.io, so far you can check out the project at https://github.com/nixcloud/nixcrates (joachim and paul are super people, hit them up if you're interested in contracting them) the net/http stuff is currently incompatible with the most recent changeset, I'll get working on it tomorrow morning HKT to make it work, I have to refactor it to suit the new stabilized API. Anyway, this attention was a bit earlier than expected, still have a couple of weeks to go before stabilizing. I hope you guys can kick the tires, tell us what you don't understand and please comment on the API because we want something sensible. We're using the late Pieter Hintjens' C4 so please hop on board and collaborate!
There is too much cognitive dissonance between nix and cargo. It might be better to get nix, a package manager, to do the job of cargo, a package manager.
Not sure if it's valid, but there's an implementation of a flow-based programming system over at https://github.com/fractalide/fractalide. Although it's not quite at the boxes and lines stage yet, the components are reusable and efficient.
Fractalide is a Rust programming platform that makes it simple to reason about efficient microservices.
The Nix Expression language provides a language compatible with a Continuous Integration - Hydra (https://nixos.org/hydra) and Code Deployment - Nixops (https://nixos.org/nixops) and when combined with Flowscript, Fractalide's own actor oriented dataflow language, the two languages fuse beautifully to become a glue language that declaratively describes your microservice architecture, then lazily builds it, weaves it together and deploys it.
Soon we'll be stabilizing at 1.0, but it's suitable to take it for a spin now, especially with the new net_http module (github.com/dmichiels/frac_net_http)
We're using the C4 contribution contract, so you're welcome to contribute code!
