3 ms·
You have no idea how much Express.js sucks on larger projects. A pain in the ass.
by joshxyz 4y ago
You have no idea how much Express.js sucks on larger projects. A pain in the ass.
- domlebo70 4y agoHow so?
- jaynetics 4y agoZero predefined structure
- joshxyz 4y agoLots of reasons: - Code cleanliness: their code almost looks like code golfing. Hard to debug. - Dependencies: everyone has different ways of implementing everything. some are even outdated. some even have stale bots that close legitimate but unattended issues. - Performance: fastify and uWebSockets.js beats express.js on benchmarks. see https://www.fastify.io/benchmarks/ https://www.fastify.io/benchmarks/ and https://github.com/uNetworking/uWebSockets/tree/master/benchmarks https://github.com/uNetworking/uWebSockets/tree/master/bench... - Multi-part parsing: this is built-in with uWebSockets.js. on express your options are multer or busboy. - WebSocket Server support: this is built-in with uWebSockets.js. on express your options are using ws and socket.io. - WebSocket pub/sub: built-in with uWebSockets.js There are better alternatives like the following: - https://www.fastify.io/ https://www.fastify.io/ - https://github.com/uNetworking/uWebSockets.js https://github.com/uNetworking/uWebSockets.js - https://github.com/kartikk221/hyper-express https://github.com/kartikk221/hyper-express
- stoicjumbotron 4y agoThoughts on Nest.js?
- joshxyz 4y agoNest.js uses express.js and socket.io underneath. uWebSockets.js beats both on performance benchmarks. In fact it beats everything based on Node's built-in http module, such as fastify, hapi, koa. https://github.com/uNetworking/uWebSockets.js https://github.com/uNetworking/uWebSockets.js
- nazka 4y agoI will trade ease of use over performance everyday. I can code in Rust but Rails or NestJS can work just fine.