Well, if people can't read a language, they can learn it. Most DSLs take to few hours to maybe a weekend to learn. Not understanding a language is not really a

Well, if people can't read a language, they can learn it. Most DSLs take to few hours to maybe a weekend to learn. Not understanding a language is not really an issue when it is so small than you can easily learn it on demand. Being able to follow the basic flow can require as little as a few minutes of explanations form a co-worker. Familiarity plays a huge role when deciding between different DSLs. Are we going to use good old JSON or that new thing that is technically a little better? Yeah, let's use what we know already. Would we decide to not use any interchange format at all because no one has ever worked with JSON? Nope. Similarly, I don't know many workplaces that outright ban using regular expression even though chances are not everyone is exactly fluent in reading them. If you language is good, fits a new use case that other languages don't and has good tooling, people will use it. The good tooling part can not be underestimated here.