Top all-time · #20921
Liasion
Company blog · liaison.dev/blogwebprogramming
Liasion is the company blog at liaison.dev, writing about web and programming. Since 2019, 3 different Hacker News readers have linked it 9 times. No feed was found, so read it on the site itself.
A field guide to the full stack: the interface, web, application, data and infrastructure layers that full stack developers work across.
What Hacker News says?
About API versioning, the problem is the same as any web API. It's possible to add backward-compatible changes, otherwise, you need to fork the backend into a new endpoint. About interoperability with non-JS environments, I wrote an article about that: https://liaison.dev/blog/articles/How-about-interoperability...
Comment linking /blog/articles/How-about-interoperability-oy3ugk
on “Do we need a web API?”Submitted Do we need a web API? as a story · 86 points
HN discussionThis has nothing to do with JSON RPC. Liaison uses Deepr ( https://liaison.dev ) as a communication protocol. Regarding the number of XHR calls, to be accurate, it is not 6 but 4. Once Liaison is complete and optimized, the number of calls should drop to 2. Also, please keep in mind that Liaison is made for building single-page applications. So, using it for a simple blog might not be the right choice. And about you…
Comment linking /
on “Do we need a web API?”Submitted Show HN: Liaison 1.0 – Dramatically Simplify Full‑Stack Development as a story · 7 points
HN discussionSubmitted Do We Need to Separate the Model from the UI? TLDR: No as a story · 4 points
HN discussionSubmitted Simplify Full-Stack Development with a Unified Architecture as a story · 3 points
HN discussionSubmitted Do We Need a Web API? as a story · 2 points
HN discussionSubmitted Show HN: Liaison 1.0 – Reuniting the frontend and the backend as a story · 1 points
HN discussionSubmitted Show HN: Liaison 1.0 – Build a Full-Stack Web App Two to Three Times Faster as a story · 1 points
HN discussion