Forcing everyone to use ourFetch is rubbish, but forcing everyone to use axios is clean and elegant? You might want to elaborate just a little more.

▲

KronisLV 2 hours ago | parent [-]

ourFetch is more likely to be buggy, unmaintained, undocumented and nobody knows it well because the guy who wrote it left the org 2 years ago and so you have to waste time reading and maintaining it yourself.

Axios is something where you get most of that work done for you by the community for free, and a lot of people know it. As long as you don’t get pwned due to it. Oh and you will actually find community packages that integrate with it, vs ourFetch, which again, nobody knows or even cares that it exists.

Applies to web frameworks, databases and other types of software and dependencies - if you work with brilliant people, you might succeed rolling your own, but for most people taking something battle tested, something off the shelf is a pretty sane way to go about it.

In this case it’s a relatively small dependency so it’s not the end of the world, but it’s the exact same principle.

	▲	DougBTX 23 minutes ago \| parent \| next [-]
		> In this case it’s a relatively small dependency so it’s not the end of the world, but it’s the exact same principle. An alternative world-view is: "A little copying is better than a little dependency," from https://go-proverbs.github.io Does become subjective about what "small" and "little" are though.
	▲	mattmanser 2 hours ago \| parent \| prev [-]
		Exactly, I completely agree. It's the difference between using a SQL library and some person on your team writing their own SQL library and everyone having to use it. There's a vast gulf between the two, professionally speaking. People dissing axios probably suffer from other NIH problems too.