3 ms·
Many of those communication barriers and interfaces are a feature, not an obstacle. For example, in a typical enterprise application it's good to know that SQL
by HelloNurse 6y ago
Many of those communication barriers and interfaces are a feature, not an obstacle.
For example, in a typical enterprise application it's good to know that SQL queries and web resource access control (two typical DSL uses) cannot interfere with one another accidentally.
- bborud 6y agoSQL is a DSL that is fairly heavy in that a lot has been invested in it over multiple decades. (It even has extensions or outgrowths that turn it into more of a general purpose language) This results in ample tooling, lots of documentation, multiple implementations, some of which are really good and a lot of community knowledge. One may like or dislike SQL, but it is undeniable that it is useful to and mastered by a great many people. Most DSLs have few or none of these properties. In some environments DSLs tend to be presented as something you can create casually. That it is a lightweight solution. And what starts as a small solution can often grow - usually to a point where not having put in a lot of work in the basic design will make the language unsound. I don't think DSLs are a lightweight solution at all. I think that giving inexperienced programmers the idea that DSLs are is something they ought to be designing probably isn't helpful.