Closed josealejandro2928 closed 1 year ago
Personal opinion: I don't think the benchmark list should include a module published one week ago.
The list on the readme should provide value to the user to compare frameworks ready to use in production.
For the same reason, I think we should clean the list actually from:
@fastify/benchmarks opinion on my previous message?
I really wish my npm package could be included in the benchmarks, even though it doesn't reach the fastify numbers, it has 100% compatibility with express since I based it on the middleware pattern and therefore all popular packages based on express middleware run, but I improved the routing algorithm which allows it to have a higher performance in the benchmarks for more complex schemes like api's that reach 100 endpoinds. It is also faster than koa and hapi. I know it's young but this is my contribution to open source. It could be included.
El sáb, 11 feb 2023 a la(s) 15:00, Manuel Spigolon @.***) escribió:
@fastify/benchmarks https://github.com/orgs/fastify/teams/benchmarks opinion on my previous message?
— Reply to this email directly, view it on GitHub https://github.com/fastify/benchmarks/pull/293#issuecomment-1426777573, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2QHWKR4BU5QRYZILVJFKDWW6LRHANCNFSM6AAAAAAUTBJY6E . You are receiving this because you modified the open/close state.Message ID: @.***>
@fastify/benchmarks opinion on my previous message?
+1
I agree with @Eomm. Closing this PR.
I added another library that I wrote. "mini-express-library"