So here we are on Independence Day again... 3 Years after the Philadelphia Conference:
Among the scattered developments in that time...WebAssembly hasn't just been kept working across the various changes to Emscripten. But it's gone further like I indicated...with WASI, we are now Cloud-ready: (sort of, see post for caveats)
Ren-C is Now on the Clouds ☁️ with WASI
So things might seem slow as you'd expect for the efforts of a few people (who are mostly me). 
But the goal is to focus on the timeless elements. I think that can pay off eventually, so long as things keep clicking in place, and luckily many are.
But as it's Independence Day, I want to draw attention to getting @rgchris back into the Revolution. We've struggled with an issue that he has felt the language direction has drifted from what he wants (at least as forum posts he can understand suggests.)
And he thinks the only way he can continue is if he develops and defines his own Rebol variant--his own sandbox-- called R3C (for "R3-Chris" or R3-Conservative")
But we shouldn't see the idea that someone would not run a stock Ren-C as a failure, but rather the person who twists it to their tastes is precisely the right customer.
The point of the language isn't that Carl--or I--solve all the representational problems someone might have... but to admit that we can't know your problems better than you do. So the goal is to give you something with enough linguistic plasticity that you can bend it, and bend it fluidly and effectively.
My attempts to design the language aren't to tell you how to code, but to build and justify a clean baseline that anyone can bend. For convenience in a random project I would bend things to be ugly, just like anyone would, if it suited the purpose. I just don't want the Ren-C core to carry baggage that is tailored to a specific use pattern...but makes it hard to use elsewhere.
Just wanted to reiterate that point, as the fireworks explode outside. Viva la Rebolution.
