Measuring Github Stars only shows popularity, not quality.
Also, there is a difference between being lazy and being efficient. Isn't driving a car lazy if you can just walk?
The problem about Express is that gluing modules that are not created to work together will only cause headaches. Also Express is poorly designed. Trying to use async/await will cause memory leaks and/or crash your app, the routing is not deterministic, and it is full of bottlenecks. Just search up Netflix's experiences with Express and you will see what I mean.
You probably didn't do your research well... And the Author of the Netflix post admitted to using Express API wrongly... Which caused their issues.. they fixed their codebase and the issue was gone.. PS that was express V1 Express is on V5... stackoverflow.com/questions/273045...
How do async await cause memory leaks... You're talking like an inexperienced engineer. .. You only have memory leaks in a badly designed application.
Express doen't know how to handle async/await. If an error is thrown inside an async handler, instead of the error being handled correctly it throws an UnhandlesPromiseRejectionError in Node 15+ and can cause memory leaks in below versions
I've tried almost all framework (express,koa,nest,adonis,feathers,hapi,etc) and i think Express wins from them all by simplicity. I'm using express with/out Typescript for 5 years and it works very well with no issue. If you face UnhandlesPromiseRejectionError, you might not use try/catch in the first place. Yes, by default it doesn't handle that error. If you face some problems in Express, belive me it's not the framework fault, sometimes its dev lack of knowledges.
And for Romain Lanz article, mostly not true and he tends to drop Express because he is one of the Adonisjs contributor.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Measuring Github Stars only shows popularity, not quality.
Also, there is a difference between being lazy and being efficient. Isn't driving a car lazy if you can just walk?
The problem about Express is that gluing modules that are not created to work together will only cause headaches. Also Express is poorly designed. Trying to use async/await will cause memory leaks and/or crash your app, the routing is not deterministic, and it is full of bottlenecks. Just search up Netflix's experiences with Express and you will see what I mean.
dev.to/romainlanz/why-you-should-d...
You probably didn't do your research well... And the Author of the Netflix post admitted to using Express API wrongly... Which caused their issues.. they fixed their codebase and the issue was gone.. PS that was express V1 Express is on V5...
stackoverflow.com/questions/273045...
How do async await cause memory leaks... You're talking like an inexperienced engineer. .. You only have memory leaks in a badly designed application.
Express doen't know how to handle async/await. If an error is thrown inside an async handler, instead of the error being handled correctly it throws an UnhandlesPromiseRejectionError in Node 15+ and can cause memory leaks in below versions
I've tried almost all framework (express,koa,nest,adonis,feathers,hapi,etc) and i think Express wins from them all by simplicity. I'm using express with/out Typescript for 5 years and it works very well with no issue. If you face UnhandlesPromiseRejectionError, you might not use try/catch in the first place. Yes, by default it doesn't handle that error. If you face some problems in Express, belive me it's not the framework fault, sometimes its dev lack of knowledges.
And for Romain Lanz article, mostly not true and he tends to drop Express because he is one of the Adonisjs contributor.