Hacker News Reader

Comment by chrisandchris | Hacker News Reader

If they also realize that having less dependencies makes deployment easier we have gone full circle.

I can't believe how many devs think dependancies are completely cost free...

Dependencies and code are both liabilities with maintenance costs. Devs chronically underestimate the cost of both, myself included.

I don’t get it, the dependencies are either needed or not. If needed that are either pulled from a project or written. So how are dependencies evil , is the rage against feature bloat pulling in dependencies ? Then the issue is the bloat

Functionality is either needed or it isn't, but it doesn't need to come from an external dependency. When it does, it probably comes with functionality you didn't need too. And as soon as you have a compile/runtime dependency on external code, your compile/execution environment needs to always have access to third party code. So that's bloat and complexity. You also give up control. Hopefully it ends up saving a bunch of time over developing it internally.

Hopefully an upgrade to an external library doesn't end up including another dependancy that happens to include some backdoor that steals all the credit card information in your database. Or a crypto miner in frontend code. Or introduces a bug that stops people from being able to checkout. Or the money package starts calculating slightly differently than your payments provider... Etc. etc.

Or even just plain remove the API you were using in yet another redesign.

Which version of react-router are we on by now? Surely it must be done by now :-/

> I don’t get it, the dependencies are either needed or not.

Some developers' judgement about needed dependencies can be suspect though: https://news.ycombinator.com/item?id=29241943

This topic is beaten to death in Philosophy of Software Design - I really, really do recommend it.

instead of CI/CD pipelines and a million dependances, why don't we just put all of the containers, like, on one single VM? and just make it a linux box or whatever?

(presumably read in Adam Something's voice)

The usual way to deploy such things is actually to create 1 VM for that application, install podman, and then run all those tons of containers in that VM. Because you cannot trust software vendors to not do or require stupid shit like requiring the docker socket, mounting overly broad volumes from the hosts filesystem, provide working and non-stupid compose/helm/...-files and things like that. Often the support contract also requires a specific version of a specific OS, a specific kubernetes distro or something like puppet/chef/... for deployment. Since for the multitude of software vendors and requirements, we couldn't easily fulfill all those at the same time on the same kubernetes cluster or infra, we just split it up into VMs.

Reply on news.ycombinator.com