this post was submitted on 26 Jul 2024
502 points (96.1% liked)
Programmer Humor
19564 readers
583 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's been baseline since March of 2017.
I've never run into a case where I've needed to use axios in almost a decade of being a professional web developer. It's mostly been an annoyance whenever I've come into contact with it, and replacing it with fetch() calls would've solved those issues.
Besides that, axios is a dependency for functionality that is already built into the web platform.
Unless you need to account for compat (DoD, gov't contractors), easy cancellation (e.g. polling is necessary vs pubsub), upload progress (e.g. progress bars for large uploads), or better errors (axios throws on server errors, fetch, by default, replies OK).
It's also nicer to configure - though I suppose you can just build classes for each fetch client on the frontend. Middleware - in particular, is easier in axios for advanced auth flows.
Native fetch is great, but saying no one uses one of the most installed (per weekly) packages on npm is just outright wrong.
Then again, this is a weird hill for me to die on so I'll leave it. The confidence of your statement was just...strange. And for some reason I was compelled to comment.
Those are all just a compilation of special cases...
I didn't say nobody uses it. There are so many projects using it, and I think no professional should be defaulting to including axios in their project unless absolutely necessary.