fayoh

You just lack imagination. Some hikvision security cameras (the large, very expensive enterprisey ones) restart every couple of days due to “buildup of cosmic radiation”.

No matter how competent you are as a developer, there is no escaping cosmic radiation! 😉

Must be closeted, she was married to three men. https://en.wikipedia.org/wiki/Git_Gay

Not saying that we don’t build technically better satellites today compared to Hubble. But Hubble is just not made to image the earth.

Just like Hubble cannot take a good picture of the earth, the satellites that do will not take an image of the crab nebula comparable to Hubble.

Right tool for the right job.

The crash early, crash often approach of Erlang has made for some amazingly resilient systems.

One time on a project I was working on, some horribly broken code was merged (nobody in the team had even heard of reviewing code). As soon as a specific call was made, it was executed once and then the thread crashed. The only way we noticed was that response times increased with load. All data and behavior was still correct. Whole nodes could go down and all you notice is a dip in performance until it comes back online.

Of course it requires special care in designing. Everything runs in stateless server threads with supervisors restarting them as needed. This in turn requires some language support, like lightweight threads. Our application would happily run tens of thousands of threads on an ancient sparkstation.

Hmm, I’m not quite well read enough to understand this. I was thinking about running this in an LXC container, does the removal of non Docker setups mean that I would have to nest Docker in the LXC container? 😕