Ah, alright. Trendy does have a negative connotation with it as well; as opposed to “established” i.e. this trend will pass. Also, note the addition of “data formats that are around today” is clearly a jab at the age of JSON and nothing else.
Saying the data format that’s easier to work with and parse while being nearly as old is trendy, is kinda disingenuous, no?
JSON, which has been around since 01, is trendy?
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.
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.
What’s wrong with axios? Quite a bold claim. Do you just want to sound smart?
IT people casually telling users to turn off all the breakers for 30s
Just be better lmao
Me, buying a 4070 super on the company’s dime
Which one was riding the horse
Companies writing code be like: my source code
Companies using libraries be like: our source code
Holy shit
Ngl that’s kinda badass
Aliven’t
My thing is imports. Like, why, why do you delete it right after I typed it in and saved?
A monad is just a monoid in the category of endofunctors, what’s the problem?
Your source is missing a bunch of chromium-based browsers to add up to 100%, and there’s no methodology or statistics explanation.