Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In this case it is entirely planned work: Anyone depending on docker.io chose to make their processes dependent on online endpoints with whose operators you have no business relationship. An unpaid third-party service going offline should be far from unexpected and if you rely on it you better be ready to cope without notice.

This is like complaining that you have to put out a fire because rather than fixing the sparking cables you have been relying on your neighbor to put them out before the become noticeable and he only gave you a short notice that he'd be going on vacation.



> Anyone depending on docker.io chose to make their processes dependent on online endpoints with whose operators you have no business relationship.

This does not somehow make the work “planned”. That has a specific definition and this ain’t it.

Some people may have called it out as a risk when it was implemented. But that still doesn’t mean it’s planned.

Someone may have included an explicit report on how to deal with it at that time. That still doesn’t make it planned.

Also, just because it’s known to be a risk and may have a chance to happen in the future does not make it expected either. Nor planned.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: