> you can't code anything without async
I'd like to understand what you mean by this. As soon as you introduce network requests in a system, don't you need to deal with asynchrony?
I'd like to understand what you mean by this. As soon as you introduce network requests in a system, don't you need to deal with asynchrony?
Asynchronous code should be intentional and deliberate in my opinion, but in modern JS/Node it is the default which leads to all kinds of crazy workarounds, callback hell and race conditions. Node has the same issue PHP had now, where green devs will crank out code without realising they need to be watching out for these things.
Is it cool that a .forEach loop could be async? Heck yeah, should it be the default? The shit people write around .forEach loops suggests, maybe not!
Callback hell? When was the last time you gave an honest effort into JavaScript?
My team and I don't write callback hell, it's just a very common pitfall and you still see it all the time. You can't bubble wrap everything I suppose.