[Huge thanks for the detailed reply, esp. network implementations] Yeah, I'm sorry, too, but I think it was the right choice to give up. Yes, you can do all t

[Huge thanks for the detailed reply, esp. network implementations] Yeah, I'm sorry, too, but I think it was the right choice to give up. Yes, you can do all the things with JIT you say, but if you look at Jonesforth, and see how it implements the assembler and so forth, you can see just how simple it is, and how much more complex it would be to build a system to deal with r^x protection. That alone might more than double the complexity and code size, maybe even more than that - maybe I'm overly pessimistic. I think it's against the spirit of jonesforth to do so. I couldn't really call the result jonesforth anymore. BTW, I was planning on porting https://github.com/narenratan/jonesforth_arm64_apl/blob/master/jonesforth.S https://github.com/narenratan/jonesforth_arm64_apl/blob/mast... which has some lovely APL sugar on top of Forth. Re: network stack, you're probably right. There ARE 1-2 network stacks in FORTH, but they are not open source. One is from Taygeta (https://www.taygeta.com/networking/forthnet.html https://www.taygeta.com/networking/forthnet.html). Porting UIP might be fun.