3 ms·
I love threads like this, it's so stereotypical JS. OP asks if it's the de-facto choice which it objectively is, but everyone recommends their pet project or fa
by ThrowAway1922A 3y ago
I love threads like this, it's so stereotypical JS. OP asks if it's the de-facto choice which it objectively is, but everyone recommends their pet project or favourite library instead.
- elaus 3y agoTo be fair for me the first 10 root comments almost all recommend Express or Fastly, no obscure pet projects or anything. So there does seem to be a pretty clear consensus.
- eyelidlessness 3y agoFWIW I was planning to respond “yes, it is the de facto solution, even if I wish it weren’t” and probably leave it at that. Granted I don’t have my pet project to recommend (I left it behind with previous employer), and maybe I would if I had it to recommend. But I’d still acknowledge first that express is the de facto solution. Also FWIW, there are a bunch of other popular options… but nearly all of them have roughly the same interface and follow the same general principles as express. Again, I wish it weren’t so. But you’re right, that isn’t responsive to the question being asked.
- preommr 3y agoDemonstrably untrue. Out of the 21 top level comments, all but two mentioned one or more of: fastify, express, kora, hona, adnos, bun/elysia Half of them recommended Fastify. Other results: 3 express, 2 hono, 2 bun/elysia, 1 adnos
- catlover76 3y agoBy what measure is it objectively standard? I can't imagine someone starting an ExpressJS application today. Every place I have interviewed at in the past several months who uses Node on the back-end said they use NextJS.
- flagged24 3y agoNext.js doesn't exclude ExpressJS. It's actually not that uncommon for self hosted Next.js instances to have a custom server setup with ExpressJS.