I've found more recently I want to solve problems with domain specific languages, so I'm totally on board with that. I would say that making dsls to solve problems is a great way to engineer software, as the code is usually testable and you don't need to modify it. Sort of where functional programming meets solid. Maybe not the best approach if you're in a startup though.
Sounds like you understand the pros and cons of DSLs: If you have a high functioning, disciplined software engineering team, a good DSL can smoke your competitors. If you don't have such a team, a DSL can smoke you.
I've found more recently I want to solve problems with domain specific languages, so I'm totally on board with that. I would say that making dsls to solve problems is a great way to engineer software, as the code is usually testable and you don't need to modify it. Sort of where functional programming meets solid. Maybe not the best approach if you're in a startup though.