Live data from Hacker News

Ask HN: Is Express still "de-facto" for building Node back ends?

news.ycombinator.com

81–90 of 100 posts

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#81
post #53

Earlier quoted context omitted.

some people use the word abandoned... some people use the word "finished"

indeed. I hate projects that make changes for no reason. If it does everything its supposed to do and does it well, it's just done. Go work on something else.

> and does it well

That is very debatable.

Eg: Performance is mediocre.

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#82

Earlier quoted context omitted.

Is Express.js still even maintained? Does it still adds new features? Also switched to Fastify. It has a great ecosystem and community. It's also easy to write custom plugins.

Why does it need to add new features? I've tried building production apps on top of server frameworks that are constantly innovating, and it's a massive PITA. You can't not update because there are security fixes that you need, but the API surface is constantly changing to support the new great thing. I think it's a good sign that the most popular server framework for JavaScript has finally stabilized and isn't innov…

> I've tried building production apps on top of server frameworks that are constantly innovating, and it's a massive PITA

Oh hi there Sveltekit

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#83
post #18

I mean, it depends on who your asking. Express has effectively been abandoned. In 2023 many would recommend Fastify as a go-to.

Has it been abandoned or is it just done? It's still sitting at 29 million downloads a week, so while it doesn't get frequent updates I wouldn't call it abandoned unless there are major security flaws that are being left unaddressed. Not every package needs to have multiple updates in a year.

Abandoned.

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#84
post #18

I mean, it depends on who your asking. Express has effectively been abandoned. In 2023 many would recommend Fastify as a go-to.

Isn’t v5 of Express expecting to drop soon (albeit, that has been the promise for a while now)?

Who knows. They were working on http2 6-7 years ago and it hasn't arrived. I was under the impression the primary dev stopped working on it and some people were able to get maintainer access for security updates but that's about it. Maybe some people re-started development but not sure and Fastify has an express compatibility layer so it's not compelling to me.

2023 I'm only thinking about express if a legacy app using it falls in my lap.

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#85
Express is still the "go-to" now, because it's the rare case of a Node library that's stable, battle-tested, and doesn't change much. (Yes, the maintainers having not been able to release v5 has actually been a sort of advantage.)

But, there are other great options to go with now, and you probably won't go wrong with fastify or hapi.

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#86

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.

By 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.

Next.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.

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#87
post #2

I used to do more node work, and that was mostly pre v4. Express was the go-to. There’s more options out there now. I did a bit of research a few years back, and my go-to now is Fastify. https://fastify.dev/

Nice. First time I hear about fastify.

I use Go for all backend. But sometimes I have dabbled in node using express.

Maybe if I ever have a need to do something with node I’ll try with this.

Cheers

Re: Ask HN: Is Express still "de-facto" for building Node back ends?

#89
post #83

Earlier quoted context omitted.

Has it been abandoned or is it just done? It's still sitting at 29 million downloads a week, so while it doesn't get frequent updates I wouldn't call it abandoned unless there are major security flaws that are being left unaddressed. Not every package needs to have multiple updates in a year.

Abandoned.

Care to elaborate on why you believe that?
Post reply on HN