[racket] DSLs and complexity

Subject for discussion:

http://firstround.com/article/The-one-cost-engineers-and-product-managers-dont-consider#

Interesting sentence in the middle:

Consider DSLs, abstractions and the attraction to being the one to build 
a framework that gets leveraged for years.


I think Racket is a different target: education vs. engineering (is this 
true?). As a software
engineer, I really agree with the article. Complexity is almost always a 
terrible thing,
whether it is a DSL, a complex implementation of a simple interface, or 
just the
one additional thing requested by product management that didn't fit.

For Racket: are DSLs a source of complexity? Or would you argue that 
they reduce the
complexity normally introduced with DSLs?

John



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20130621/0a4f5b5e/attachment-0001.html>