cowboyd

6 ms·

1.
by cowboyd 5mo ago
I think writing an effect library yourself is a tough ask, but some of them have gotten really, really good. And they get you things that are simply not possible with promise. Check out Effection if you want a more vanilla javascript syntax
2.
by cowboyd 5mo ago
Is it safe to just "stop calling next() on a generator?" like the post suggest? To me that sounds like dropping the task on the floor. Specifically, this will not invoke any finally {} blocks: More correctly, you should invoke `re
3.
by cowboyd 2y ago
JavaScript generators are unmined gold! We've done a lot of usage of JavaScript generators as delimited continuations; using them to implement the classic shift/reset operations in JavaScript. https://github.com/th
4.
by cowboyd 3y ago
> yes but what do I say to my colleagues when they realize they need to learn generators (it's a non-trivial hurdle for many people) Just tell them that they already know them. `yield*` is - a superset of `await` so if you understan
5.
Effection 3.0 – Structured Concurrency and Effects for JavaScript(frontside.com)
6 points by cowboyd 3y ago|2 comments
6.
The Await Event Horizon in JavaScript(frontside.com)
6 points by cowboyd 3y ago|2 comments
7.
by cowboyd 3y ago
JavaScript’s async/await constructs have a critical lack of power which makes them unsuitable to implement structured concurrency.
8.
by cowboyd 4y ago
For those interested in exploring Structured Concurrency in JavaScript, there is https://frontside.com/effection
9.
by cowboyd 4y ago
I think the simplest expression of the idea of structured concurrency that I've come across is this: The scope of any concurrent process is the same as the lexical scope of the function that created it. This has profound implications
10.
by cowboyd 5y ago
> I'm not sure I buy the premise for the library's existence, at least with how the author describes it. Just do a google search for "structured concurrency". These ideas did not come out of a vacuum, but instead from