<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hono on Gaurav.dev</title><link>/tags/hono/</link><description>Recent content in Hono on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/hono/index.xml" rel="self" type="application/rss+xml"/><item><title>Express, Koa, or Hono for Your Next TypeScript API?</title><link>/posts/express-koa-hono-typescript-api/</link><pubDate>Sat, 18 Jul 2026 00:00:00 +0000</pubDate><guid>/posts/express-koa-hono-typescript-api/</guid><description>&lt;p&gt;Express shaped the Node.js API ecosystem. Koa refined its middleware model, while Hono brought a compact, standards-oriented approach to edge and multi-runtime applications. All three can serve a TypeScript API, but their strengths appear under different constraints.&lt;/p&gt;&#10;&lt;h2 id="express-optimise-for-familiarity"&gt;Express: optimise for familiarity&lt;/h2&gt;&#10;&lt;p&gt;Express remains the lowest-risk choice when hiring reach, middleware availability, and compatibility dominate the decision. Its programming model is widely understood, integrations are plentiful, and almost every hosting platform can run it without explanation.&lt;/p&gt;</description></item></channel></rss>