3 ms·

> You either place faith on a build step working deterministically when it was not designed to work like that I'm sorry, what? Why would a build not work deter

> You either place faith on a build step working deterministically when it was not designed to work like that I'm sorry, what? Why would a build not work deterministically? > If you decide to put faith on your ability to run deterministic builds with a potentially non-deterministic system If your build is non-deterministic, how can you have any faith in the binaries it produces? You would have much larger problems in that case. > You use git to track changes, regardless of where they came from You probably don't want to do that if it is 70% of your codebase and slows down all your developer's git. > Then you need to have internationalization test steps for each localization running as part of your integration tests to verify if your build worked I'm convinced you've never used a build system before. Your build should fail if required files are missing. Downloading translation files at build time from some artefact repository vs storing them in git is how a lot of companies do it.

arinlen 4y ago
> I'm sorry, what? Why would a build not work deterministically? Because they don't and never did? Do you understand build systems and individual tools were not designed to ensure deterministic behavior? https://reproducible-builds.org/docs/deterministic-build-systems/ https://reproducible-builds.org/docs/deterministic-build-sys... Anyone with any professional experience developing software can tell you countless war stories involving bugs that popped up when building the exact same project separate times. What leads you to believe that translations are any different? In fact, more often than not we see unexpected changes during translation update steps. > If your build is non-deterministic, how can you have any faith in the binaries it produces? First of all, all builds are not deterministic by default. To start to come close to get a deterministic build, you need to do all your own legwork after doing all your homework. Did you ever did any sort of this work? You didn't, didn't you? You're not looking and are instead just placing blind faith on stuff continuing to work by coincidence, aren't you? > You probably don't want to do that (...) Yes, I do. Anyone with their head on their shoulders wants to do that. It's either that or waste time tracking bugs that you allowed to go to production. Do you want to waste your time hunting down easily avoidable and hard to track bugs? Most of the professional world doesn't.

arinlen 4y ago

> I'm sorry, what? Why would a build not work deterministically? Because they don't and never did? Do you understand build systems and individual tools were not designed to ensure deterministic behavior? https://reproducible-builds.org/docs/deterministic-build-systems/ https://reproducible-builds.org/docs/deterministic-build-sys... Anyone with any professional experience developing software can tell you countless war stories involving bugs that popped up when building the exact same project separate times. What leads you to believe that translations are any different? In fact, more often than not we see unexpected changes during translation update steps. > If your build is non-deterministic, how can you have any faith in the binaries it produces? First of all, all builds are not deterministic by default. To start to come close to get a deterministic build, you need to do all your own legwork after doing all your homework. Did you ever did any sort of this work? You didn't, didn't you? You're not looking and are instead just placing blind faith on stuff continuing to work by coincidence, aren't you? > You probably don't want to do that (...) Yes, I do. Anyone with their head on their shoulders wants to do that. It's either that or waste time tracking bugs that you allowed to go to production. Do you want to waste your time hunting down easily avoidable and hard to track bugs? Most of the professional world doesn't.