-1
composition and pipeline-operators are both INCOMPATIBLE with
javascript's async-programming style, and will likely result in
tech-debt when used. its fairly common for blocking-code to evolve
into async-code as features are added, e.g.
```js
result = arg |> operator1 |> operator2 |> operator3;
// becomes spaghetti-code when operator2 evolves
// to require async-merging with database-queries, file-reads, etc.
...
operatorAsync2(arg |> operator1, function (error, data) {
if (error) {
...
return
}
result = data |> operator3;
...
});
```
On 8/25/17, Simon Staton <[email protected]> wrote:
> That link appears to be broken Naveen, If you are considering a similar
> approach let’s collaborate would be interested to get your outlook on this
> and we could probably expand on either of these
> _______________________________________________
> es-discuss mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/es-discuss
>
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss