tl;dr - Arc comes with a DSL designed for just the sort of problem described in the Arc Challenge. What really matters is the ability to create DSLs.
I worry that the challenge will eventually be dominated by over-specialized DSL's. Arc may have libraries that are particularly beneficial to accomplishing this challenge, but the functions and macros used to do so are not of a wholy different "language" from those used in everyday arc prgramming.
Hi Daniel, can you give us some examples of the sorts of DSLs you're playing with? The title ("Answering the arc challenge") led me to expect code snippets.
Deleted comment
For general publication, sure. When engaged in a blog discussion about programming language design, it is customary to take a certain level of jargon-awareness for granted. For instance, the author also does not explain CGI, DAL, JSONP, html, ASP, or RSS.
It's expanded on the first occurrence in the body text...
No point in making the title unnecessarily long. Besides, that's what gets you to read the article.