4 ms·
> 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 need
by NayamAmarshe 2y ago
> 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 https://hono.dev) now, which is like Express.js but better.
- makerdiety 2y agoYou know what, I thought Next.js was a backend framework. I must be thinking of something else. I mistakenly have confused one thing with another. So never mind lol
- moogly 2y agoYou might be thinking of Nest.js.
- thr0w 2y ago> Setting it up was a hassle and so was hosting it. How is it possible that there are people active in this industry who think setting up Express is a hassle?
- 52-6F-62 2y agoThey got promoted to senior+ and run the show. “Greybeards go home, the future is now”?
- wruza 2y agoHow does one set up express and host a web server correctly? >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.