[Red Daly's Parenscript Object System, simplified-CLOS-like.]
@abuseofnotation @screwlisp @sigue
Thank you, that is impressive.
From Stanford.
Regrettably, I don't have the time to find out the extent of simplification.
[Red Daly's Parenscript Object System, simplified-CLOS-like.]
@abuseofnotation @screwlisp @sigue
Thank you, that is impressive.
From Stanford.
Regrettably, I don't have the time to find out the extent of simplification.
[CLOS and JavaScript]
> parenscript obviously doesn't have its own CLOS implementation
And achieving that doesn't seem like a five-minute job...
I am not the judge of whether that work can be justified, no matter how attractive it is.
@trurl what do you think of replacing Microsoft Typescript with this:
1. Write a book of defuns in #ACL2 #lisp, with supporting theorems in a separate book
2. Prove theorems about functions in ACL2
3. Load the defun-only book in common lisp and #parenscript it into javascriptland
?
Full disclosure I'm a long-standing skeptic of web designers normally getting what they think they're getting out of Microsoft Typescript.
I'll work on the docu to #slurm-cl tonight #lisp #hyperapp #parenscript #webframework
My own web application framework for #lisp and single page applications. using #parenscript #hyperapp #wookie #tachyons
hope you like it.
Ok i'm ready.
I've written a web framework for #lisp where you can write your frontend and backend code entirely in lisp.
It uses #hyperapp as frontend technology in combination with #parenscript and #wookie at the backend.
It is somehow inspired by #redux where you simply dispatch actions to the backend and at the backend side you define functions which define what to do next.
just take a look at http://gitlab.com/m3tti/slurm-cl
and drop me a note.
Made some mods to sigil, the command line tool for #parenscript.
I turned on case-sensitive identifiers and added a verbose mode that lets you control whether or not to include your parenscript source as comments in the output