From 7cdf02f9713a4f5687bb9cac6b1346054c26d6f1 Mon Sep 17 00:00:00 2001 From: Artem Date: Wed, 25 Jul 2018 20:55:09 +0300 Subject: [PATCH] A minor typo fix --- iguana/exchanges/mm2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/iguana/exchanges/mm2.md b/iguana/exchanges/mm2.md index 62ea08a06..b04be0919 100644 --- a/iguana/exchanges/mm2.md +++ b/iguana/exchanges/mm2.md @@ -47,7 +47,7 @@ The benefits we want to reap from this are: * Hot reloading. When the code is separated from state, it's trivial to reload it, both with the shared libraries in CPU-native environments (dlopen) and with WASM in GUI environments. This might positively affect the development cycle, reducing the round-trip time from a failure to a fix. Implementation might consist of two layers. -A layer that is ported to the host environment (native, JS, Java, Objective-C, cross-compiled Raspberry Pi 3, etc) and implements the TCP/IP communication, state management, hot reloading all, things that won't fit into the WASM sandbox. +A layer that is ported to the host environment (native, JS, Java, Objective-C, cross-compiled Raspberry Pi 3, etc) and implements the TCP/IP communication, state management, hot reloading, all things that won't fit into the WASM sandbox. And a layer that implements the core logic in a stateless manner and which is compiled into a native shared library or WASM. Parts of the state might be marked as sensitive.