4 ms·
This makes no sense. In order to build a service, you need a library (or something very much like it) supporting it. If you need a library, and can use a libra
by geophile 6y ago
This makes no sense. In order to build a service, you need a library (or something very much like it) supporting it.
If you need a library, and can use a library, yay, you're done, it's the simplest and fastest thing possible. If, for some reason, the logic you need can't be run locally, then you need a service. Find or build one and use it. You will pay in application complexity, dealing with the possibility that the service is down/unreachable. You will also pay in latency.
Why is this "not even wrong" article at the top of Hacker News?
- chrisrhoden 6y agoLooking over the rest of the conversation here, there's a clear bias in a lot of areas to build services when a library would suffice. You're agreeing with the article, and seem to be suggesting that your agreement represents a universal viewpoint, but it does not seem to.
- geophile 6y agoYes, we are both saying "use a library when possible". I am mystified by the need to write or read such an article. It seems akin to "don't use an airplane to go to the corner store for a dozen eggs".
- human 6y agoYou’re right but your service could be exposed with a public API and still have your library public. I think the best of both worlds is to have an open-source library and a service. People can choose the one they prefer. And you can still make money from selling the service.