Hello, all! It might sound a little bit weird, when i tell you, that recently standardized Webassembly Containers in your browser are - Lisp machines.
Emscripten C/C++ "emcc" compiler does not translate into machine code directly, but rather some kind of meta machine code (Intermediate Bytecode), that the processor (Intel, ARM, ...) then can easily JIT - transform into its final, executable machine code. That Intermediate Bytecode, in fact, is a pure Lisp, just like PicoLisp is: https://developer.mozilla.org/en-US/docs/WebAssembly/Understanding_the_text_format PicoLisp and Webassembly containers have a lot in common. They even have same capabilities, features. Nothing speaks against letting PicoLisp run directly in a browser container or - serverside as Webassembly container. PicoLisp thus - was far ahead of its time! Here a famous quote by the Docker inventor on twitter: https://twitter.com/solomonstre/status/1111004913222324225 Solomon Hykes @solomonstre <quote> If WASM+WASI existed in 2008, we wouldn't have needed to created Docker. That's how important it is. Webassembly on the server is the future of computing. A standardized system interface was the missing link. Let's hope WASI is up to the task! </quote> PicoLisp *is* a genius strike, but some get it at least a decade later ... :-( Even Microsoft now is on the train to port its ASP DOTNET CORE 3.0 Blazor Library onto Webassembly Lisp: https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor https://github.com/AdrienTorris/awesome-blazor/blob/master/README.md It's just ridiculous! Have fun! Happy easter and keep away from Windows and other viruses! Guido Stepken
