Re: [whatwg/fetch] Use case for Headers getAll (#973)

A key challenge is that end users don't really care whether the code is running in the browser, on the edge, or in a server, they would like the APIs to be consistent and for us not to have different APIs for the same things in different environments. So, while I definitely understand the position and WHATWG's mission, where there is known existing overlap in functionality/API between these different environments, it would be great to avoid diverging APIs. If necessary to make progress, we can get Node.js, Deno, Workers, and other backend/edge environments together to collaborate on these things but it would also be great to recognize that "the web" is not limited to just web browsers.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/973#issuecomment-961253303