[arminluschin]

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.

[evnix]

Have to agree on this one. As a current user of Hono, I'll just switch to a proper router.

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

[kkielhofner]

Same. IMO Hono + Workers seems to be somewhat of a hidden gem but this largely comes down to Workers, of course.

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?

[eddd-ddde]

Not too long ago I discovered itty-router and since then it's the only thing I need for my APIs.

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.

[cosbgn]

Same, I'll probably move to https://github.com/unjs/h3 since it's used anyway in Nuxt (which I use for other projects)

[lf-non]

Yeah, I like Hono, but it was surprising to see a react alternative from them. I am not sure why they are trying to compete with preact/atomico.

[drewbitt]

Doesn't seem right to me either. Of note though, it has not bloated the core and you can continue using the backend portions the same as before.