RAM you mean. ROMs cannot be loaded into... except EEPROMs

my ignorance is very forgiving

Let’s make this easier with an illustration. This is just based on my understanding of async programming in other languages. Suppose we have 8 OS threads prepared to run coroutines, and we create 50 coroutines (representing 50 request connections). The mapping here is m:n, meaning 8 OS threads will execute 50 coroutines. Now, imagine 8 requests come into our server: 1. We spawn 8 coroutines. 2. Our 8 OS threads pick them up and execute them. 3. One of the requests makes a Postgres query. 4. The query code runs → we pause that coroutine → the OS thread is now free and can pick up another coroutine (because the thread is not blocked). 5. After some time, the query result is ready. 6. One of the OS threads resumes the paused coroutine and continues execution until it’s done. So far, everything looks good. But what if one of the requests involves 8 minutes of heavy computation inside its handler? Here’s what happens : A new connection arrives → wrapped in a coroutine → an OS thread picks it up. This coroutine contains pure CPU-bound work. Unlike IO tasks, CPU tasks should not be paused. IO can run in the background while the OS takes care of it, but CPU computation requires an OS thread to keep running continuously. If we try to pause this coroutine, we’re also pausing the computation itself. So: If the computation takes 8 minutes, but we pause it for 1 minute → the total latency becomes 8 + 1 = 9 minutes. Pausing/resuming repeatedly just makes it slower and adds pointless delays. Now, let’s improve this by moving long running CPU tasks to a separate dedicated thread pool: A new connection arrives → wrapped in a coroutine → one of our 8 OS threads picks it up. The coroutine sees a long CPU task → instead of blocking, it delegates the work to the dedicated thread pool: > “Hey bro, give me one OS thread from your pool to handle this heavy task. I’ll go back to serving new requests.” The dedicated thread pool runs the heavy computation until it finishes, then returns the result to the user. Meanwhile, the connection handler thread has already moved on to accept and execute other coroutines. If a coroutine needs to wait for IO → it pauses. If a coroutine needs heavy CPU work → it gets delegated to the dedicated pool. This way: No request handler thread is ever blocked. No CPU computation task is paused (which would only delay results). Request handling remains fast and responsive, because the handler threads are always free to accept new work. IO tasks → can be paused safely, no problem. Long CPU tasks → should not be paused. Instead, offload them to a dedicated thread pool so request handling stays smooth. (And true paralel)

And we don't do cloud because it is overpriced crappy service

when we get AI-only ASICS or SOCs .... will that change? or if isolated to only running on a quiet GPU, will that be any different?

He wants to believe that OS thread is forever blocked by the high CPU operation until it releases

is this implying what is called a RACE CONDITION???? :)

I do not understand what you are talking tbh 😅

Hey guys, I made a helper library wrapper for Linux NTSYNC. It provides Windows Events and Semaphores and almost 100% compatible except it has no support for named events, semaphores, and APC. Suggestion and feedbacks are welcome! https://gitlab.com/kawaiighost/libntsync/

Anyone from india starting coding now

The more i study the more i need to go deep and it gets deeper and deeper

Sorry this ot but Does anyone have the python grp link?

Sorry this ot but Does anyone have the python grp link?

You use python

Anyone from india starting coding now

i gotta turn c++ source to pure C. Therse stl, std in it..

Hey, my college have an option to either learn C or learn CPP, what should I learn?....can you please tell that with reason

export?

no, cpp to pure c. Like objects to structs, vector strings to normal strings etc.

Hey, my college have an option to either learn C or learn CPP, what should I learn?....can you please tell that with reason

Old tasking compiler had c++ implemented literary in preprocessor :D I was pretty surprised when I tried to use preprocessor to expand macros and includes and I got C code instead of c++ :D

Hey, my college have an option to either learn C or learn CPP, what should I learn?....can you please tell that with reason

i also think about it. is there any you can recommend? or smth like c++ to IL to C

I have a project to do in c. Can someone help me with it I can pay

Homework/assignment?

when the c++ going to be destroyed by Rust?

when the c++ going to be destroyed by Rust?

Either one or another? Personally, I would go with C++, you will learn it eventually anyway, and it is more complex, so more stuff to learn. But I'm biased, I never learned C myself.

C from learning pov, C++ has great standard libraries for abstraction (which is not good for learning, also its add complexity)

First question that should be asked is, why it needs to replace?

Not soon 1. Rust sucks for many things, like game development, when you need fast code but also to iterate and discard fast. Rust is slower for development, and it takes even more time to make it fast (and at that point you probably have a few unsafe blocks and some unsound code there as well) 2. There is a lot of legacy code written in C++ that nobody will update while it works (why would they)

I work with embedded netwoking system (switches and routers); nobody bothers to change even a line of working code

Every change has a chance to introduce new bugs associated with it, and the more used the system (or the bigger the amount of money that depends on it working), the more scary it is. And changing to Rust wouldn't give any benefit to most of the systems anyway.

Not soon 1. Rust sucks for many things, like game development, when you need fast code but also to iterate and discard fast. Rust is slower for development, and it takes even more time to make it fast (and at that point you probably have a few unsafe blocks and some unsound code there as well) 2. There is a lot of legacy code written in C++ that nobody will update while it works (why would they)

I think saying “many things” is a bit over the top. For me, it really depends on the use case and how skilled the team is right now. I also think Rust isn’t the best fit for game programming, C++ has Unreal Engine with decades of development behind it. From my own experience on an Intel i5 10th gen with 20GB RAM, compiling Rust and C++ projects that use third party libraries takes about the same amount of time. I’ve used Tokio, Libcoro, and Photonlib, and honestly the compile times felt pretty similar. Where Rust really shines, in my experience, is on the server side things like backends, game servers, and real time servers. The ecosystem there is already mature, and the documentation is easy to find and understand since it’s centralized on one site. By contrast, C++ library documentation can be scattered and sometimes hard to digest. I came from Go, and found that Rust is easier to master and produce high quality code (no memory mistakes, race conditions in safe Rust and less sneaky performance pitfalls). I have built some backends in C++, it ran, but when I benchmarked it, the performance was actually below Go and Java (it is “my C++ skill issue ><”). But in working with raw pointers in Rust feels almost the same as in C++ (the other safeties are still on, only raw pointer is same like in C++). That’s why I see C++ as great for the super low level parts, while Rust fits better a bit higher up the stack especially if the team doesn’t have super deep low level expertise. I use translation :)

> no [...] race conditions I have found plenty of race conditions in Rust code. The "fearless concurrency" crowd writes very shitty concurrent code and trusts the pretty basic concurrency protections of Rust way too much

ymmv but in terms of overall experience Rust delivers higher quality code especially with concurrency

I am sure that is deadlock sir, not race condition. Because the compiler would stop if a non Send and Sync object were sent to another thread.

Spewing that Rust fixes race conditions altogether is the same rhetoric I was served with Java 15 years ago, and yet race conditions still slipped through and caused outages

We still have TCP half-open like 10 years after the Zookeeper shitstorm

TCP is OS managed no?

Like many other things indeed, and the OS will have a blast introducing race conditions to your "safe" rust code

Could this be prevented in other programming languages?