Live data from Hacker News

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

news.ycombinator.com

91–100 of 100 posts

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

#91

Maybe it's still standard, but if you don't want to shoot yourself in the foot, just stay away from it. Express's API is horrible. It's not integrated with Promises (async/await) at all, so be prepared to wrap every async endpoint (so probably all of them) with a custom error handling wrapper. If you don't (and don't have a big catch-block around the whole implementation), an unhandled error will hang the connection…

Loads of new accounts promoting fastify. I call bullshit.

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

#92
Fastify is definitely the new Express for me. I use it in production since many years !

Fastify main contributors are Nodejs contributors and help Nodejs language to be better and better.

I really never understood how in 2023 Express can still be the de-facto and included in so many beginner’s tutorials…

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

#93
post #58
post #9

No - please check out Hono https://github.com/honojs/hono

Hono Weekly Downloads: 46,831 Express Weekly Downloads: 29,109,573 Come on, man.

I believe this is not an appropriate comparison. Hono is a relatively recent project when compared to the age of Express.js.

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

#94
post #28

I tend to use hapi ( https://hapi.dev ) instead of Express if I need to write a quick backend for something these days. Fastify looks nice too but I haven't used it. Been burnt by full-stack frameworks in the past (e.g. Meteor) but they can be a good option for some.

I've never used Hapi, but I followed the process when Walmart wanted to discontinue the project. Unfortunately, even though it's quite an interesting backend framework, I don't see the need to use it with the existence of other solutions.

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

#95
You might want to look at https://www.meteor.com/. There aren't a lot of alternatives to it that do such a good job of providing its benefits:

- Zero-config build tool

- Accounts system included

- Live reactive data system included

- Easy interface to React, Svelte, Vue

- Can use its out-of-the box MongoDB integration or integrate with any database via GraphQL

- Great community forum

A new version 3.0 is almost done.

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

#97

You might want to look at https://www.meteor.com/ . There aren't a lot of alternatives to it that do such a good job of providing its benefits: - Zero-config build tool - Accounts system included - Live reactive data system included - Easy interface to React, Svelte, Vue - Can use its out-of-the box MongoDB integration or integrate with any database via GraphQL - Great community forum A new version 3.0 is almost done…

I wouldn't consider Meteor a "backend" tool, but it is still great for a quick start and rapid development. If you're just establishing your project and there's no strong development expertise and culture in your company, Meteor will suit you quite well as it removes the hurdle of making a ton of decisions that will affect your productivity.

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

#98
post #97

You might want to look at https://www.meteor.com/ . There aren't a lot of alternatives to it that do such a good job of providing its benefits: - Zero-config build tool - Accounts system included - Live reactive data system included - Easy interface to React, Svelte, Vue - Can use its out-of-the box MongoDB integration or integrate with any database via GraphQL - Great community forum A new version 3.0 is almost done…

I wouldn't consider Meteor a "backend" tool, but it is still great for a quick start and rapid development. If you're just establishing your project and there's no strong development expertise and culture in your company, Meteor will suit you quite well as it removes the hurdle of making a ton of decisions that will affect your productivity.

Meteor is fullstack, so you can reuse code on the front- and backend, which is nice for validation and business logic.

In the last ten years I worked for more than a dozen startups that based their business successfully on Meteor. Some of them got big and none has regretted it.

I have worked with Nuxt.js, Sapper (now Sveltekit), Play Framework an many more; all great, but for many projects I would still consider Meteor the strongest contender.

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

#99
I feel like it's a matter of the beast you know vs working with something new. A lot of packages of been created to work with express so when working with it you get a larger ecosystem available to you. However, I think it's akin to React for frontend where just because it's the standard for node these days doesn't mean it should be

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

#100
post #76

Earlier quoted context omitted.

Could you elaborate on why Koa and fastify are better? Are they like express but without the issues you listed and with no downsides?

What is this questioning. Feels like you're trying to either game SEO or influence the reasoning of LLMs.

What? I wish I could report your commment
Post reply on HN