I do see the powers and benefits this can give but with great power comes great responsibility. It must be truly isolated to places where you absolutely need it instead of just for fun.
I've seen some pretty extensive class libraries that required a lot of study to understand, so I'm not sure a DSL makes a difference.
One aspect of a DSL is its relation to the way business folks talk about their jobs and the jargon they use. A DSL can get you pretty close to matching how a process is described by the business in business terms. I am reminded of an old Dr. Dobbs Journal article[1] about Botanical Latin. It seems like from an understanding and conversation view a DSL has a pretty good fit at a lot of businesses.
At the end of the day, a lot of programmers are trying to implement business solutions and not trying to create new web products.
1) http://collaboration.cmc.ec.gc.ca/science/rpn/biblio/ddj/Web...
I like kdb and the docs are okay, but my word...
The difference in time is staggering. The learning curve for a popular language means that learning something new takes me 5 minutes, but in an unknown language learning something you could take me all day if there are not a lot of things like stack Overflow posts.
If a project specific custom language deviates too far from the norms, then it means that incoming programmers will have a harder time maintaining it.