Message from JavaScript discussions

January 2019

— That's a terrible solution


* It's not composable
* Enforces impure, stateful pipelines
* Leaves more memory than necessary hanging around in a process
* Is itself a stateful operation

— Lots of problemos

— Got solutionos?

— What solution you are reffering? 1, it's not for composition, compose something else. 2, dont use it, 3, it doesnt leave anything un-needed 4, dont use it

Message permanent page

— But i think it will conquer minds of async freaks🤤

— 1. A general solution for handling async should be composable, in that it should model return values and eventual failures in a way that is flat and repeatable, halting is just too primitive to be practical for these things, promises allows us to not care about whether or not it's async since it has the composable property.

2. I won't.

3. Lots of things, safety for instance.

4. I won't, and rest of JS community won't either.

Message permanent page

— It's a normal threading primitive, hence it doesn't make sense in JS

— It's like a spinlock

— Terrible

— What about the opposite?

— If you had the ability to spawn threads and not wait for them