do you prefer?
worker-pooled and event-driven
This question is too simple to answer properly
I haven't heard that before!
A single thread should be able to handle many concurrent connections, but multiple threads should be possible too
https://t.me/c/1204549490/8635
would that be ok for a game server where there would be probably calculations too ?
What about cpu intensive cases?
Answered right above your message lol
I hit the send button before I saw it.
Are you aiming for benchmarks or for real world use cases at this point? Drogon-core and actix-core seem to be aiming for highest score in benchmarks, that doesn't really tell anything about real world use cases like game servers or cpu intensive tasks. These have different requirements and different opportunities for optimization
You are right. But I chaned the topic. Forget about that.
Mate, I'm sorry to say this, but you'll need to improve your OS knowledge before starting with your plan of coding a web framework.
It doesn't relate. Web dev is not a system dev. So it is not necessary to know that.
Plus this. I don't really understand what you're trying to do. On one hand, you want to start an overly ambitious project to be the absolutely fasted ever, on the other hand you're lacking the very basic knowledge to even remotely get close
By OS knowledge I mean the stuff about processes, threads, deadlocks, etc. I'm not talking about UNIX system programming or anything close for the matter.
Well, kinda true but then it's not applicable here
Creating a web server framework is not really web dev
You can't go fast if you don't understand what's happening with the code you write
Yeah, web development is HTML, CSS, JS, WebAssembly(new).
Yes. And creating a web server framework is none of that. The web server doesn't care if you're serving HTML, css or js. It just sends some text over http(s)
Yeah, right. I am new to Rust.
That's got nothing to do with Rust
Same applies to node (express.js or whatever) or go or c++ or python
And system programming.
I hate Express.js by the way. I use Fastify.js.
I didn't get that.
If you're interested in reading books, I'd suggest "Operating System Concepts by Peter B Galvin"
No, that's just how http works. The client requests a file and the server provides it. What content the file has is (mostly) irrelevant for the process and the server, that's up to the client to handle
Congratulations, you missed the point of my message and the topic of this group. I don't care what nodejs framework you use
As far as async programming is concerned, found this piece very informative https://unixism.net/loti/async_intro.html
That might be a bit late now ^^
Обсуждают сегодня