What async promised and what it delivered
causality.blog
What async promised and what it delivered
1–10 of 317 posts
Re: What async promised and what it delivered
#2Surely by section 7 well be talking (or have talked) about effect systems
Re: What async promised and what it delivered
#3I like async and await.
I understand that some devs don’t want to learn async programming. It’s unintuitive and hard to learn.
On the other hand I feel like saying “go bloody learn async, it’s awesome and massively rewarding”.
Re: What async promised and what it delivered
#4I like async and await. I understand that some devs don’t want to learn async programming. It’s unintuitive and hard to learn. On the other hand I feel like saying “go bloody learn async, it’s awesome and massively rewarding”.
> It’s unintuitive and hard to learn.
Funny, because it was supposed to be more intuitive than handling concurrency manually.
Re: What async promised and what it delivered
#5I like async and await. I understand that some devs don’t want to learn async programming. It’s unintuitive and hard to learn. On the other hand I feel like saying “go bloody learn async, it’s awesome and massively rewarding”.
> It’s unintuitive and hard to learn. Funny, because it was supposed to be more intuitive than handling concurrency manually.
It is a tool. Some tools make you more productive after you have learned how to use them.
I find it interesting how in software, I repeatedly hear people saying "I should not have to learn, it should all be intuitive". In every other field, it is a given that experts are experts because they learned first.
Re: What async promised and what it delivered
#6I like async and await. I understand that some devs don’t want to learn async programming. It’s unintuitive and hard to learn. On the other hand I feel like saying “go bloody learn async, it’s awesome and massively rewarding”.
> It’s unintuitive and hard to learn. Funny, because it was supposed to be more intuitive than handling concurrency manually.
It is. A lot.
But concurrency is hard and there's so much you syntax can do about it.
Re: What async promised and what it delivered
#7Earlier quoted context omitted.
> It’s unintuitive and hard to learn. Funny, because it was supposed to be more intuitive than handling concurrency manually.
It is a tool. Some tools make you more productive after you have learned how to use them. I find it interesting how in software, I repeatedly hear people saying "I should not have to learn, it should all be intuitive". In every other field, it is a given that experts are experts because they learned first.
Except you're hearing it from someone who doesn't have a problem handling state machines and epoll and manual thread management.
Re: What async promised and what it delivered
#8[deleted]
Re: What async promised and what it delivered
#9I like async and await. I understand that some devs don’t want to learn async programming. It’s unintuitive and hard to learn. On the other hand I feel like saying “go bloody learn async, it’s awesome and massively rewarding”.
> It’s unintuitive and hard to learn. Funny, because it was supposed to be more intuitive than handling concurrency manually.
It IS intuitive.
After you’ve learned the paradigm and bedded it down with practice.
Re: What async promised and what it delivered
#10I like async and await. I understand that some devs don’t want to learn async programming. It’s unintuitive and hard to learn. On the other hand I feel like saying “go bloody learn async, it’s awesome and massively rewarding”.
I can't follow that it's hard to learn and unintuitive