[langsec-discuss] langsec on granular level

Geoffroy Couprie geo.couprie at gmail.com
Tue Feb 23 10:14:43 UTC 2016


This looks interesting! Do you have other examples than the NOT gate?
Have you explored running the components in different processes or
machines communicating over the network?

I'm happy to see nom put to good use!

Best regards,

Geoffroy Couprie

On Sat, Feb 20, 2016 at 6:28 PM, stewart mackenzie <setori88 at gmail.com> wrote:
> Hi all,
> I've been a lurker for a while.
> We've reached a point our platform is stable enough for use by others.
> github.com/fractalide/fractalide
> It's a flow-based programming platform implemented in Rust.
> Components have input and output ports each requiring an evolvable
> capnproto contract.
> Therefore we get the Rust goodness of speed without compromising
> memory safety (I know there are folks on this list whom are human
> compilers and write 100% memory safe C code, many of us are not of
> this caliber!)
> We've adopted Nix as our package manager so this means:
> 1) we're the first to do so :-)
> 2) a component can setup its own OS level libraries (whatever is
> available in nix we can use)
> 3) the repository can expand massively as nix is a lazily evaluated
> language, meaning you only compile what you need.
> We're able to achieve a high degree of reusability and
> maintainability. FBP localizes logic to specific components. A fix in
> one place very propagates to wherever the component is used.
> Lastly, we use the excellent parser combinator implemented by Geoffroy
> Couprie (https://github.com/Geal/nom) to parse the graph layer
> coordination flow script.
> Hope some find it useful.
> Happy hacking!
> /sjm
> _______________________________________________
> langsec-discuss mailing list
> langsec-discuss at mail.langsec.org
> https://mail.langsec.org/cgi-bin/mailman/listinfo/langsec-discuss


More information about the langsec-discuss mailing list