I liked the comment before I finished reading it

😮

​@@TieMajorI know your message before reading it.

I was awaiting your comment.

Ofc it can

Why the placeholder

​​@@igz5553asynchronous commenting with promises

Promise rejected with this one 🗣️🔥🔥

@@igz5553 async promise

Uncaught (in promise) ERR_INTERNET_DISCONNECTED

I bet you like red tea. I had figured out that ordinary tea that I liked is called "red tea" around the world but it has black color.

The function strtok() in the standard library can be thought of as a coroutine.

Fuck Isreal too 🤣🤣🤣🤣😁

Use an array or some type of linked structure to store the tasks sequentially and you can just iterate backwards.

You are correct. Coroutines are sort of an abstraction over an event loop, where you run on a single thread, and functions can yield in turn when they wait for I/O operations or other coroutines to complete. They are run by a built-in scheduler, like the os scheduler for threads, but there is no preemptivity (i.e the scheduler cannot forcefully stop a function). It is important to note that you can combine coroutines and threads, for exemple by running coroutines in a thread pool, if you need that sort of thing. In that case you can have subordinate event loops that can send events to the main event loop when tasks are finished.

I think the non-Go-branded term for goroutine is "Green threading"

I think a more important axis is cooperative vs preemptive scheduling: - cooperative: you stop running by manually yielding (you or the language but you won't get stopped if you don't) - preemptive: you get (forcefully) paused after some time by the OS. It will later resume your program. This happens many times per second. You don't have an unlimited amount of cores so eventually, 2 different processes will take turns sharing a core/thread. IMHO, the distinction between process and thread is good to know if you have to pick one but you can always ask the OS to share some memory with another process if you want to. A coroutine is just the fancy name of a function that can pause itself (can produce a payload) and can be resumed (optionally with a payload). It is good to have if you're doing cooperative scheduling but you can do the same with callback. AFAIK, goroutine are a backlog of coroutine to run spread across executors (i.e. thread) that run them sequentially. They yield when doing channel and OS i/o (roughly). So enough infinite loop will hang a go application. If you want to mess around with a naked coroutine, Python and JavaScript's generator fit the description: - yield keyword for explicit... well yielding - optional payload both ways (method .send in Python and .next in js)).

@@valshaped And Green processes would be a combination of coroutines and processes. E.g. what is used in the Erlang runtime

From a hardware point of view: processes are separate virtual memory page tables, the timer interrupt handler routine invoked by the CPU and provided by the OS will determine which page table pointer to assign based on the scheduler. threads are separate stack pointers. that same timer interrupt handler routine will then change the stack pointer to the one belonging to the thread in the process that the scheduler thinks should run and calls iret instruction which pops the instruction pointer from the stack and runs from there. The other stuff is software abstractions.

but that's basically what async/await is, an FSM, the rest is just fattening syntactic sugar.

In fact, clang allows `const` as well.

He edits text files. And then relies on external tools to eventually transform them into executable instructions. It is called prgramming, it is a real thing, look it up!

@@theevilcottonball I don't care, it is much boring.

@@BolasDear ???? how did you end up here?

@@angelcaru i thought he was making marshmellows recipes thas why i am here , actually i was roaming on american invention for some fun, i got this channel . most boring man on earth , he still had not answered my query where to get programming socks . in my city no body sells theose .see he makes jokes still i took them seriously.

@@theevilcottonball have you heard anyone who says i dont know windows , is it possible being a human and not knowing windows?

JOSHUA? WTF

@@lowlevelcodingch wild Joshua caught in the wild

cool

Very bad language

Femboy god (Thor and Loki crossdressed too lmao)

Honestly, back in the day we had stuff like that - Logo programming language. It put off more people than I can think of.

Raylib is an abstraction on top of OpenGL/Vulkan/Metal/Direct3D

Because he already used OpenGL and said that it sucks to literally copypaste the same stuff again and again and go through the same bugs again and again instead of just asking library "give me a window" and "draw rectangle there and flip the screen". Vulcan is just more annoying OpenGL that sucks less in terms of API and performance, but he literally draw a teapot in browser at 60 fps only with his old-ass Intel-i3 10-years old laptop's CPU.

Always been there

tea temperature looks like broken

I think he just wants to reach an international audience. The russian stream was just an April fools joke

But why not in english? If you have trouble understanding what he says, then this is perfect opportunity to improve on the language. It just more accessible for everybody to speak and write something in one well-understood language (in 21 centuary it's English, like it or not). If streams will be only in Russian you will get people who speak Russian, not people who searched for C programming, neural networks programming, Ada programming... I hope I stated my point clear.

Больше людей в мире знает английский.

As far as I understand whenever he calls update on his Tasks they are advanced one step at a time by interpolating and then basically yielding. When there is a Taskgroup the Tasks are executed pseudo parallel, meaning one task is advanced by one step then the next is advanced by one step and so on. The code look sync because it is.

firster

Shame on your ass 🤣🤣🤣