Programmer Humor

19606 readers

1097 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

[email protected]

497

I am a software developer at PornHub (pixelfed.de)

submitted 3 months ago by [email protected] to c/[email protected]

78 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (2 children)

What's wrong with axios? Quite a bold claim. Do you just want to sound smart?

[–] victorz 2 points 3 months ago (1 children)

What's wrong with fetch()?

[–] [email protected] 2 points 3 months ago (1 children)

Nothing, as far as I can tell. Besides being relatively new, it seems to have basic things you need.

So what's wrong with axios? Asking the inverse doesn't answer my question.

[–] victorz 1 points 3 months ago* (last edited 3 months ago) (1 children)

Besides being relatively new, it seems to have basic things you need.

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.

[–] [email protected] 1 points 3 months ago (1 children)

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.

[–] victorz 1 points 3 months ago

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.

[–] victorz 1 points 3 months ago

Do you just want to sound smart?

lol, nice addition.

No. There's just rarely a legitimate reason now to use axios. It shouldn't be the first recommendation on which to build your API fountain.