Why using express instead of Hono? #8149
Replies: 1 comment
-
The problem with using the newest, shiniest framework available is that it'll only stay new and shiny temporarily. However development must happen regardless. As I write this there are already several newer, shinier alternatives to Hono (For example: ElysiaJS) - why use Hono when you can use Elysia? Please don't take this personally, but if you are picking your framework purely based on 'speed' then there is something deeply wrong with your process. Nevermind that when you eclipse a certain codebase threshold that ALL frameworks essentially become 'slow,' you pick the right tool for the job. Let's consider ExpressJS. First and foremost, for a company that expects to be in business for a long time, how easy is it to find Express devs? Easy. Express has been around for ten years now, and will continue to be around for the foreseeable future - built by elite developers with decades of experience, knowledge, and know-how. How many of these new frameworks can say the same? I have a hard time following and agreeing with the claim that Express isn't performant enough. It most certainly is for 99% of use-cases. Express was the right choice. The Payload team are a group of seriously talented devs, and it shows with almost every decision they make. |
Beta Was this translation helpful? Give feedback.
-
Why using express instead of Hono?
Hono is much faster than Express
Beta Was this translation helpful? Give feedback.
All reactions