I only ever used hono as a simple convenience router for my cloudflare functions. This feels ambitious. I’m a bit skeptical if this is the right direction frankly, I hope it doesn’t make the framework too bloated.
I don't want those SSR oddities and react like "hooks" sneak into our backend codebase. They have been a constant source of confusion, bugs and performance issues in our frontend app.
Let me save you from typing the obligatory HN response: YoU DoNt HaVe tO UsE ThOsE
The performance (and especially pricing) is pretty wild and combined with various bindings (R2, KV, D1, AI, etc) general Cloudflare stuff, free egress, etc it can provide significant advantages.
That said looking at this I’m confused, to put it mildly, and I may start looking elsewhere. Back to itty-router?
It's extremely minimalist, I just create a context object and implement in it any functionality I need such as headers, error handling, anything.
I even use it for "CLIs" that I then call with curlie.