> I can just imagine the learning curve when encountering legacy code in a language that's only used for the project, product, or company. I've seen some prett

> I can just imagine the learning curve when encountering legacy code in a language that's only used for the project, product, or company. 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/Website/articles/DDJ/1995/9509/9509k/9509k.htm http://collaboration.cmc.ec.gc.ca/science/rpn/biblio/ddj/Web...