4 ms·
heya HN: in this article I argue for using hypermedia for your application API, once you've realized that your app and your general data APIs have different nee
by recursivedoubts 5y ago
heya HN: in this article I argue for using hypermedia for your application API, once you've realized that your app and your general data APIs have different needs
would love feedback
- harryvederci 5y agoThanks for htmx! I recently noticed a similar issue in my side project, your timing with this article was perfect for me :)
- henryfjordan 5y agoI think the article which yours is based on is attacking a bit of a straw-man, at least now that 5 years have passed. The original complains of needing to write an application-specific API in addition to a general-purpose API but techniques like Redux/Sagas or GraphQL have helped to build that "Application Specific" data-layer in the frontend on top of general APIs. Now-a-days you query that general API and build your application-specific data layer in the browser before rendering that to HTML using React or a similar framework. In this new world, sending Hypermedia instead of JSON over the wire is still a very compelling idea (why send JSON and make the browser process it?) but maybe it would be best to explore how to accomplish that from within a React-Server-Side-Rendering layer instead of pushing that logic all the way down to the Backend-API layer.