Splitting Your Data and App APIs Up: Going Deeper
htmx.org
htmx.org
Don't build a general-purpose API to power your own front end - https://news.ycombinator.com/item?id=28511570 - Sept 2021 (106 comments)
Also the other other article:
Why I No Longer Use MVC Frameworks - https://news.ycombinator.com/item?id=11104356 - Feb 2016 (194 comments)
Why I No Longer Use MVC Frameworks - https://news.ycombinator.com/item?id=11041999 - Feb 2016 (2 comments)
Why I no longer use MVC frameworks - https://news.ycombinator.com/item?id=10740029 - Dec 2015 (92 comments)
would love feedback
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.
You can do marvelous things with simple `GET /api/model?ids=1,2,3`.
1. The conceptual overlap between this and React Server Components, which seems to have arrived at similar implementation details from a different set of use cases.
2. Generalizing even further by client libraries allowing you to return existing DOM nodes instead of requesting anything from any networked API.
I’m coming from a perspective where my main interest is performance of mostly static MPA websites, and where isomorphic libraries typically double bundle static content. Just as sending HTML instead of JSON on the wire might have huge optimization benefits, so too would having primitives for transferring nothing at all.