How “It works in my machine” turns to “It works in my container”

Re:How “It works in my machine” turns to “It works in my con... by nerdponx on Thursday July 27, 2023 @02:24AM (#36889666)

It's reproducible enough for most purposes most of the time. When is the last time your Python web app serving cat pictures went down because of a subtle change in the Debian Bookworm container?

[ Parent | on HN ]

Re:How “It works in my machine” turns to “It works in my con... by salawat on Thursday July 27, 2023 @06:05AM (#36891331)

...Funny you bring that up.

I was cobbling together build scripts for a mail system for Raspi/Armbian the last couple weeks. Very similar packaging stuff, but the number of little subtle differences in install/postinstall/prerm/postrm scripts took a generous level of spackling over to get just right.

Hell, once I get everything nailed down, I'm writing test frameworks for my bloody build scripts if you can believe it.

So...uh... Last week?

[ Parent | on HN ]

Re:How “It works in my machine” turns to “It works in my con... by nerdponx on Thursday July 27, 2023 @06:19PM (#36900916)

Fair enough, but I don't think that's a typical experience.

[ Parent | on HN ]

Re:How “It works in my machine” turns to “It works in my con... by ParetoOptimal on Thursday July 27, 2023 @09:14AM (#36892932)

> It's reproducible enough for most purposes most of the time.

The freedom given in ability to limit your thinking space by reproducibility should not be under stated.

[ Parent | on HN ]

Re:How “It works in my machine” turns to “It works in my con... by nerdponx on Thursday July 27, 2023 @06:19PM (#36900912)

Same with static types. Sometimes it really helps to limit yourself, other times it's setting up unnecessary obstacles with no benefit. Sometimes you want Idris 2 or Rust, and sometimes you want Ruby or Clojure.

[ Parent | on HN ]