7 ms·
People use axios or ky because with fetch you inevitably end up writing a small wrapper on top of it anyway.
by pier25 7mo ago
People use axios or ky because with fetch you inevitably end up writing a small wrapper on top of it anyway.
- afavour 7mo agoSome might say the tradeoff of writing a small wrapper is worth it given what’s been demonstrated here.
- pier25 7mo agoYeah but what about other deps like db drivers?
- jmull 7mo agoIn my experience people feel the need to wrap axios too.
- kube-system 7mo agoThese are the kind of people I hope AI replaces
- nathancahill 7mo agoAI was trained on Axios wrappers, so it's just going to be wrappers all the way down. Look inside any company "API Client" and it's just a branded wrapper around Axios.
- kube-system 7mo agoSpeak for yourself, Claude works fine with fetch on my system.
- lukeschlather 7mo agoI have never consciously wrapped Axios or fetch, but a cursory search suggests that there was a time when it was impossible for either to force TLS1.3. It's easy to imagine alternate implementations exist for frivolous reasons, but sometimes there are hard security or performance requirements that force you into them.
- zachrip 7mo agoFetch has also lacked support for features that xhr has had for over a decade now. For example upload progress. It's slowly catching up though, upload progress is the only thing I'd choose xhr for.
- apitman 7mo agoYou can pipe through a TransformStream that counts how many bytes you've uploaded, right?
- afavour 7mo agoThat would show how quickly the data is passing into the native fetch call but doesn’t account for kind of internal buffer it might have, network latency etc
- zachrip 7mo agoThat is a way to approximate it, though I'd be curious to know the semantics compared to xhr - would they both show the same value at the same network lifecycle of a given byte?