> That seems like a huge disadvantage to me. The bottle neck in any software project (> 1 person) Even single-author projects have the person who wrote the cod

> That seems like a huge disadvantage to me. The bottle neck in any software project (> 1 person) Even single-author projects have the person who wrote the code months ago and the person reading it today. :) > is usually the time it takes to read and understand source code. Some estimates[1] claim that up to 78% of development time is spent just reading code. Sure. This is a big deal. I'm not sure the software-conservative approach of locking down the syntax and flexibility of expression is deeply helpful, though. My experience is that comprehending syntax (while it can be a barrier) isn't the biggest portion of that 78% you're talking about -- maybe 15%. Wrapping your head around the semantics of what a piece of code does is a much bigger portion. The semantics of what the software does are the true language of the program you're writing, so in a sense the choice isn't whether or not you're going to have a DSL or not, it's just how concisely the syntax of the language will support the expression of it. And I've found that the less flexibility you have in syntax, the more likely it is over time that you'll have to type/read over larger amounts of code in order to capture the expression of a given semantic goal.