Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "asynchronous bullshit"
I get it, for quite some stuff, async is very, very useful. But why on fucking earth do so goddamn many functions NEED this (and those callback functions) and can't do without?!
If there would be good and nicely understandable await documentation that actually fucking works, I'd be so happy.
I've currently got .then after .then after motherfucking then and its irritating me to no end as it, in this context, shouldn't even be necessary. This thing I'm writing doesn't give a fuck if something takes a few milliseconds before the rest of the program can continue!!
Fucking hate Qt.
Spent all morning trying to figure out how their bullshit QThreadPool works with their bullshit QRunnable but after a bunch of bullshit asynchronous testing I figured that my thread object was being collected and deleted before I was done with it, for no reason. Now if the race condition was documented... This wouldn't be an issue. But every google search brought up nada. Eventually I resorted to turning off autoDelete on the runnable, but then I just have a memory leak, obviously.
I couldn't find a way to manually clean up a QRunnable in Python. What the fuck.
I just went back to good old fashioned QThreads... This is why I quit Qt in the first place.18
I hate you fucking callbacks. why don't you callback in the fucking order you were motherfucking called!!!! why must you force me to call a callback a callback!! 😣😡😤👹2
Fucking asynchronous code can be very annoying sometimes. Had to struggle the whole day yesterday to get it work properly so I fetch all the results from a function which does many asynchronous calls.
Then I realized that I just need two more counter variables to increase and later decreases to detect when all of them finished.
Just coded my first flutter app! The feeling when no async wait error appeared anymore was amazing. It uses the geolocation library to geht your current Position via GPS2
I love C# but I think that the addition of async/await did more harm than good. Hardly anyone can understand how to use it correctly and the only people who grok its black magic fuckery enough to write about it are MS employees. Try to do anything with it? Nope, there's a high falutin blog post by the likes of Stephen Cleary explaining why everything you know is wrong and you should have never even used async/await in the first place. Even worse is that to use the supposedly game-changing feature requires you to rewrite your entire fucking codebase.
Can you tell that I'm frustrated trying to wrap my head around async/await?4