Hi all!

Main argument was, that only with Lisp i can mathematically, formally
proof, that my programs *are safe*. Demand for safe programs, libraries of
all kinds is going through the roof.

Base was this paper here:
http://www.cse.chalmers.se/research/group/logic/TypesSS05/Extra/lectnotes_vol1.pdf

It has a good reason, why Lisp is also deeply sticking behind Webassembly,
the standardized browser container format - and - hopefully - the new
upcoming server container format, with S-Expressions at its base:

https://developer.mozilla.org/en-US/docs/WebAssembly/Understanding_the_text_format

https://github.com/appcypher/awesome-wasm-langs/blob/master/README.md

Unbelievable, all that language support, that now is translating to Lisp,
isn't it? Pure fun!

Formal verifiers - behind the scenes - then will ensure, that everything
uploaded (by customers) will precisely follow its predefined specifications
isand not doing - by evil code injection - anything other than that!
Execution will instantly terminate then. That prototype is finished now, in
the testing.

And those containers will run on ultra cheap, ultra fast - Lisp executing
ASICs with their own TCP/IP stack - in the very short future. Stay tuned.

That's why most my software now is implemented in Lisp, most parts in
PicoLisp. It's a nice, handy, easy to learn Lisp dialect and libraries are
sufficiently complete, nothing important missing.

Best of Picolisp is PILOG, the Prolog interpreter that can run on top of a
distributed, self replicating, ultra fast persisting database, that comes
for free with Picolisp, very much like (or even better) than
Closure(Script) with its ultra expensive commercial DATOMIC database.

This makes PicoLisp a total killer ... and is coming for free! That's just
unbelievable! Nothing else in the world does even come close to that
expressiveness and capabilities!!!!

Even if i am repeating myself: "PicoLisp, in its design, is a genius
strike!"

And you? What where your motives to switch to PicoLisp?

Best regards, Guido Stepken

Reply via email to