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?
All modes of transportation should be abolished because every day they're used in kidnappings, murders, and drug deals. At the very least, we should allow warrantless searches of all people based on the gut feeling of militant high school dropouts. That certainly won't be abused.
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.
I use lazyvim and this is my experience in neovim as well. I don't think it's a weird place, it just puts the onus on the end-user to tailor their experience.
ShieldGengar @ shield_gengar @sh.itjust.works Posts 0Comments 90Joined 1 yr. ago
Ah, you too, have worked for a non-profit