pfrazee
Why shouldn't I use this?
Within the README you added the following:
Oh cool, should I use this?
No.
Could you explain why? I'm not as clued in and this seems like a really interesting use case for tagged template strings and learning how HTTP works w/o using a porcelain command like window.fetch.
Sure-- so this is basically a wrapper around the request module, and that's really what you should be using. This module is fun, but it adds extra processing overhead that (afaik) doesn't really add value.
If this module just opened a TCP socket and wrote the string to that socket, then it might actually give a perf win. But you can't do that in browsers, and I'd actually be surprised if it was faster than what's in node.
Happy/interested to be proven wrong on that
On Feb 10, 2017, at 5:27 PM, Tim Branyen [email protected] wrote:
Within the README you added the following:
Oh cool, should I use this?
No. Could you explain why? I'm not as clued in and this seems like a really interesting use case for tagged template strings and learning how HTTP works w/o using a porcelain command like window.fetch.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Do you think you could just swap that out for window.fetch which also returns a Promise and is native.