Guys cover your eyes I'm gonna say two bad words inside a paragraph

Fuck JavaScript and asynchronous programming - I'm not skilled enough for this so I have to insult it periodically until I'm skilled enough to know partially more than now what the fuck I'm doing (therefore the times I use bad words when referring to js and async programming will decrease - or maybe at the increase of knowledge, my usage of bad words will augment. Only time will tell).

Thats hurt.

I am in the middle of learning both things because I wanted to do some full-stack web development in the future.

Anyway, good rant! I sometime hate it too ><

@sayasyedakmal that's nice. I wish you the best learning and getting a job in the field :)

Mhh what’s your issue with it? Is there something which you can’t understand/which troubles you more specifically?

@piratefox Especially considering how nice it in modern JS~

Is JS async harder than ajax was? I remember doing ajax.

@piratefox After writing this rant, I possibly got a +10 problem-solving buff for a period of 5 minutes - and my final, smart resolution came out as "damn, why am I getting stuck on this minor thing? Better move on and then, if I remember, go make that extra feature." The problem was: I have an array of URLs. Usually it has one, but sometimes it can contain two or three. It's OK if I only fetch the first one, but a more complete app would be checking if there's more than one, fetching them all, and storing that in the array separately so I can call React components out of them all. When I tried to implement it the complete way it gave me an array full of "Promise <state> fulfilled", so I lazied the thing out and made it the "only one URL" way. Don't worry, as I again love JavaScript and asynchronous programming (valid as of 14:41 PM, GMT -3)

@ElectroArchiver ayo just wanted to say that I've seen your work on documentation and I love it. It's pretty. Keep it up

@lessi Oh thank you very much!

Let me know if you need help with anything~

@lessi ahah glad to ear you solved it! Just be sure to leverage Promise.all to parallelise when needed, its the thing people forget the most!

What a beautiful rant ✨

Were the 2 bad words "fuck" and "javascript"?

@t3b4n eyyy chequé tu perfil y vi que eras de Santiago. sorpresa, soy de Colina. emigré desde Venezuela hace 1 mes con mi familia y ahora ando aquí, estudiando webdev. :)

@gosubinit I meant "fuck" twice as the bad words but you have a solid viewpoint as well

@Demolishun exactly. It was a nightmare, now we have better things with their own maintenance cost.

Async and await are pretty easy if you come from C# and Java. Those two languages need to use them all the time, or else your native windows app / native android app will become unresponsive from time to time, when they are doing operations which are a little bit long.