3 ms·
I agree with this - everything should be sync first and async when needed with a keyword (similar to how Go has goroutines and channels, coincidentally this is
by zackmorris 9y ago
I agree with this - everything should be sync first and async when needed with a keyword (similar to how Go has goroutines and channels, coincidentally this is how UNIX executables and streams traditionally worked). Javascript gets it just exactly backwards. Going from imperative to functional programming is like leveling up, and it's very hard to go back down to mutable variables, side effects and nondeterministic flow control. So I understand why Node devs prefer async how it stands now, but it's hard to unsee Go/Elixer/Erlang once it clicks.