@avesbury_rosetta @piegames
Absolutely 100%. There's loads of times I'm writing code and the documentation goes "it works like this really annoying way" without answering why it needs the really annoying implementation instead of doing something sane and standardized.
It would be awesome if programming was standardized like plumbing or electrical work where there was one good way to do it that everyone agreed on. But if that happens a lot of developers are going to be very, very sad.
But let me give some examples off the top of my head. Axios, one of the main packages used for web requests in Javascript, has no retry functionality built in, you can't tell it to auto-retry something if the connection blips out for a second or so, it has to be hacked together custom. For anything remotely important, you obviously want it to try a bunch of times before just giving up. There is a axios-retry package though, it just needs to be loaded in with webpack at build time, so you *have* to use webpack now, there's no non-webpack way to get the module loaded. Super aggrivating. And really there's no reason why stuff *has* to be this way.