(define (page . s) `((html (body ,@s))))
(@@: (cont (entry-lambda (:keyword foo)
(page (a/cont: (@@: (cont (entry-lambda () (page "You said: " foo))))
(input: (@: (name "foo")))
(input: (@: (type "submit"))))))
Now, beyond a certain point, optimization becomes specialization.
It's like compression. The more you know about the domain, the shorter
you make the frequent patterns, and the net amount of code gets smaller.
But how do you know you're not overspecializing?
Some of Lispers, including me, have this fear for overspecialization.
Reading arc does have an effect to cure that. I see some nice
abstractions in arc which I'd like to steal from.
I'm more curious, though, to see wider range of applications in arc
and how the core abstractions will live up.
(btw, Paul, if you read this could you reset my password in Arc forum and send it to email@example.com?)