I hate internal DSLs. What's the problem with common APIs? It it too simple using them without thinking about reflection all the time?
2
Replying to @tillsc
@tillsc What’s the difference between a good API in a good language and an internal DSL?

Jan 16, 2015 · 7:46 PM UTC

4
Replying to @stilkov
@stilkov an internal DSL usually comes with a separate object tree representing the input (like an abstract syntax tree)
1
@tillsc It does. If your architecture is naturally mapped to an engine executing some kind of model, that seems perfect
1
more replies
Replying to @stilkov
@stilkov @tillsc a good API does not try to hide the host language or put some weird semantics on its features.
1
@Developmind @tillsc true for a good internal DSL as well, right?
Replying to @stilkov
@stilkov @tillsc I admit there is a grey zone between API and DSL. You're talking about that?
3
@Developmind @tillsc Yes. I think if internal DSLs suck, it’s because they try to do too much
Replying to @stilkov
@stilkov @tillsc a good API is naturally composable with other good APIs. But often enough there is a mental gap between iDSL and its host