Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Without really knowing what specifically you are doing or having implemented it myself, isn't async at its core "just" an event loop/queue of tasks?
Code runs in a single thread. Depending on the async part, like timers, web requests or file writes, they either use an async API themselves or run in a separate thread/process. Once they are done, their result is pushed to the queue. Once the main thread finishes a task or hits an await, the next queue item runs.
That's just my understanding though, idk if it's right or useful.
for some reason I decided to re-invent async myself ground up for no reason even though I've last month taken up the philosophy "as long as it works, make it as janky as possible" which was actually very invigorating and fruitful in the end
but now I feel overwhelmed, there's no resources, I've never done anything similar, nobody else knows how to do this, the AIs don't know how to do even small basic building blocks of this, there are no similar repos, and I have self-doubts because I went against my new-found and successful principle
and also my brain feels restless and stressed as fuck because brain issues activated maybe due to change of drugs
so I kind of wanna explode and scream
and then maybe cry
and then maybe I'll exhaust myself and be able to focus again
rant
ragh