Hi Kenneth,

thank you for your interesting example that allows to get some insights into
how lisp works. However, isn't the point you are making more generally valid
for all kinds of declarative and macro-based syntax that is "compiled" to
javascript? For example, in QxTransformer, we use a HTML-like markup which
gets transformed in javascript, and with the templating capabilities of this
system, I could easily draw up examples where a few lines of xml compile to
3 or more times as much procedural javascript code. However, the drawback is
always the same - the further you get away from the code that does the
"actual stuff", the more code duplication you will have at the end... I
prefer writing my GUI in declarative XML because it is immediated obvious
what it is meant to do - just like in HTML - and thus in my opionion better
maintainable. But to have an additional layer is always a disadvantage, too.

Just my 2 cents.

Christian
-- 
View this message in context: 
http://qooxdoo.678.n2.nabble.com/ANNC-qooxlisp-0-1-qooxdoo-Common-Lisp-tp5095503p5119531.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------

_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to