It calls expressjs minimalist, but it has 52 dependencies. I really feel like we really need to reconsider what "minimalist" means in the js ecosystem.
ExpressJS vs. Actix-Web: performance and running cost comparison
51–58 of 58 posts
Re: ExpressJS vs. Actix-Web: performance and running cost comparison
#52No one has ever been deciding between express and actix-web
I have, because I did a bunch of Express+TypeScript, always wanted to learn Rust and wanted to bootstrap a business by optimizing costs. I liked this article since I always wanted to see concrete numbers or at least a general idea. It's not uncommon for business to move from Ruby/Python/JavaScript to Go as they grow. I personally preferred learning Rust over Go because of its depth.
Re: ExpressJS vs. Actix-Web: performance and running cost comparison
#53Earlier quoted context omitted.
I have, because I did a bunch of Express+TypeScript, always wanted to learn Rust and wanted to bootstrap a business by optimizing costs. I liked this article since I always wanted to see concrete numbers or at least a general idea. It's not uncommon for business to move from Ruby/Python/JavaScript to Go as they grow. I personally preferred learning Rust over Go because of its depth.
"... wanted to bootstrap a business by optimizing costs" -- The famous quote "premature optimization is the root of all evil" comes to mind. :-) As a fellow tech entrepreneur, thinking long and hard about my planned startup's technology stack, I was also guilty of initially leaning toward a scalable, safe, enterprise-y and fancy, but less mature, stacks, like C# on .NET Core and Julia, correspondingly. However, upon…
A concret example of that is in a comment in this thread: https://news.ycombinator.com/item?id=22458176
That said you partially quoted me, if it wasn't for learning Rust I would stick to Express+TypeScript. If it's bound to fail, I might as well learn and have fun doing it.
Re: ExpressJS vs. Actix-Web: performance and running cost comparison
#54They are running Node with only one worker and are instead tuning the DB connection pool in that one worker... So the whole benchmark is bogus.
Author addressed this on a Reddit comment thread: https://www.reddit.com/r/rust/comments/fbu5tt/expressjs_vs_a... . The results aren't significantly different; Rust is still very much more efficient than NodeJS especially when considering memory utilization (and the hosting costs associated with that memory footprint).
I tried to make changes and run his benchmarks, however the DB seeding is in Rust and it fails to compile on my machine....
Re: ExpressJS vs. Actix-Web: performance and running cost comparison
#55Earlier quoted context omitted.
"... wanted to bootstrap a business by optimizing costs" -- The famous quote "premature optimization is the root of all evil" comes to mind. :-) As a fellow tech entrepreneur, thinking long and hard about my planned startup's technology stack, I was also guilty of initially leaning toward a scalable, safe, enterprise-y and fancy, but less mature, stacks, like C# on .NET Core and Julia, correspondingly. However, upon…
I 100% agree with the point you are making. A concret example of that is in a comment in this thread: https://news.ycombinator.com/item?id=22458176 That said you partially quoted me, if it wasn't for learning Rust I would stick to Express+TypeScript. If it's bound to fail, I might as well learn and have fun doing it.
Re: ExpressJS vs. Actix-Web: performance and running cost comparison
#56Earlier quoted context omitted.
A real minimalist web framework for Node is Koa. Basically anything besides the bare minimum is a separate dependency, so you only install what you need. That said, it probably means minimalist in a usage sense. Compared to things like Nest.js (which I love, don't get me wrong), express is a lot more straightforward and basic.
Koa is better but still has 43 dependencies...
Re: ExpressJS vs. Actix-Web: performance and running cost comparison
#57Re: ExpressJS vs. Actix-Web: performance and running cost comparison
#58Earlier quoted context omitted.
How you generate the types from graphql. I noticed most of the generators create types with all optional keys. Do basically you need to check all the time...
If they're creating types with optional keys it's probably because that's how you're defining your types in GraphQL. E.g. with type Foo { bar: String } bar would be optional in the Typescript type because it's specified as optional in the GraphQL type. You would need to do the following to make it required: type Foo { bar: String! }