> What was wrong with Express.js?
Setting it up was a hassle and so was hosting it. It's a great tool, don't get me wrong but after using Next.js, I never needed it.
There's also Hono (https://hono.dev) now, which is like Express.js but better.
Setting it up was a hassle and so was hosting it. It's a great tool, don't get me wrong but after using Next.js, I never needed it.
There's also Hono (https://hono.dev) now, which is like Express.js but better.
How is it possible that there are people active in this industry who think setting up Express is a hassle?
>hono
Seems absolutely the same to me, their getting started shows no login mw (only already token-ed auth), and it’s just a single context param instead of (req, res, next, res.{text,json}). What’s so innovative there? Feels like yet another cute solution looking for a problem.