3 ms·
This is a bit off-topic, but am I the only one who thinks "fetch" API is weird? To me the first thing that irks me is the name itself. "Fetch". Simply because
by mewpmewp2 5y ago
This is a bit off-topic, but am I the only one who thinks "fetch" API is weird?
To me the first thing that irks me is the name itself. "Fetch". Simply because api calls that you are making don't have to be about fetching something. You can make a request to create, update or delete something. Why this type of naming? Even for retrieving information the name just seems a bit random.
- move-on-by 5y agoI was under the impression that the term Fetch was chosen because it didn’t have much overlap with existing popular libraries or a common variable name. I feel like I read that in the early days of its creation. However, I just spent a while looking for that discussion in the Whatwg spec and was unable to find it. Would love it if someone else could verify that belief. Perhaps I’m mixing it up with something else.
- zenosmosis 5y agoI somewhat agree with this sentiment (thought about it before as well), though I now tend to think of it as something like "fetching" the result of a given call, regardless of the operation type.