Why use Hono for Next.js backend (route handlers)?
I'm creating a full-stack web app and probably using Next.js API/route handler: https://nextjs.org/docs/app/building-your-application/routing/route-handlers
I saw that Hono has a page about supporting it: https://hono.dev/getting-started/vercel#_2-hello-world
I'm curious what the point of using Hono in Next.js' route handlers is, instead of just using Next.js' default route handler (using 2 solutions (both support HTTP requests/responses) instead of simply 1)? Is it because the developer may prefer Hono's syntax? (FYI I'm not very familiar with backend development)
I saw that Hono has a page about supporting it: https://hono.dev/getting-started/vercel#_2-hello-world
I'm curious what the point of using Hono in Next.js' route handlers is, instead of just using Next.js' default route handler (using 2 solutions (both support HTTP requests/responses) instead of simply 1)? Is it because the developer may prefer Hono's syntax? (FYI I'm not very familiar with backend development)
