Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Even in REST, I’m sure you don’t use every field from every request? In fact, such tight coupling between FE and BE in REST is strongly advised against. And “wasted fields” was never a problem graphql was trying to solve.


We are in complete agreement - I was criticizing the implication that it was impossible to ignore fields in a REST response.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: