4 ms·
If your API is so complicated that it becomes a DSL, then perhaps there should be better communication between frontend and backend teams. Setting up a lean API
by snicker7 7y ago
If your API is so complicated that it becomes a DSL, then perhaps there should be better communication between frontend and backend teams. Setting up a lean API contract makes more sense than creating an internal DSL or exposing internal data stores directly to users.
- throwaway1492 7y agoDo you extend this criticism to GraphQL?
- asdfasgasdgasdg 7y agoSome things are irreducibly complicated. You can't set up a lean API contract for a complicated thing without giving up power. The example of SQL is pertinent. Any attempt to set up a lean API contract for a relational database is doomed to be weak and painful to use. Without knowing the specific problem domain the blogger was dealing with, you can't know whether that was the situation. But if we assume they are competent, then we can assume a lean API was not possible.
- jacob019 7y agocomplexity != complicated
- asdfasgasdgasdg 7y agoIt literally is though. com·plex·i·ty n. the state or quality of being intricate or complicated.
- jacob019 7y agoThey exist as distinct words for a reason. The difference is important. Search "complexity vs complicated", I even found a few articles about it right here on hacker news.