Here's a table from one of my archived posts that highlight some differences of rubico and rxjs
Promise.all
Observable.prototype.pipe
If you had sync and async functions that you wanted to compose together in a pipe, with rubico it would like something like
pipe([ syncFnA, asyncFnA, syncFnB, asyncFnB, ])(someValue) // Promise { someOutput }
rubico pipe and other functions that accept functions all handle promise resolution for you. Conversely,
pipe([ syncFnA, syncFnB, ])(someValue) // someOutput
If no functions are asynchronous, you'll get a synchronous value not wrapped in a Promise
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Here's a table from one of my archived posts that highlight some differences of rubico and rxjs
Promise.all
on an array of PromisesObservable.prototype.pipe
If you had sync and async functions that you wanted to compose together in a pipe, with rubico it would like something like
rubico pipe and other functions that accept functions all handle promise resolution for you. Conversely,
If no functions are asynchronous, you'll get a synchronous value not wrapped in a Promise