The main thing you are missing is that “loose coupling” does not mean “create an interface”. You can have all concrete classes and loose coupling or all classes with interfaces and strong coupling. Coupling is not about your choice of implementation, but about which part does what.

If an interface simplifies your code, then use interfaces, if it doesn’t, don’t. The dogma of “use an interface everywhere” comes from people who saw good developers use interfaces to reduce coupling, while not understanding the context in which it was used, and then just thought “hey so interfaces reduce coupling I guess? Let’s mandate using it everywhere!”, which results in using interfaces where they aren’t needed, while not actually reducing coupling necessarily.

Perfect explanation. This kind of thing shows why tech giants are giants and why selfhosted is a niche. People like paying for convenience.

This is such a weird article. Electron is not for making http requests, it’s for rendering web pages. Nothing within curl can render web pages. I’m not saying you should be using electron necessarily, but this is just so obviously wrong, what is the author thinking?

And (almost) any programming language has a built-in primitive for making http requests (possibly even using libcurl internally), why would I switch to a command line call if I can just do the http call directly with that primitive?