3 ms·
Because when you get buggy behaviour from some library because it was compiled to a different architecture it's much easier to debug it if your local environmen
by piva00 6y ago
Because when you get buggy behaviour from some library because it was compiled to a different architecture it's much easier to debug it if your local environment is similar to your production one.
Yeah, I'm able to do remote debugging in a remote VM but the feedback loop is much longer, impacting productivity, morale and time to solve the bug, a lot of externalised costs that all engineers with reasonable experience are aware of. If I can develop my code on the same architecture that it'll be deployed my mind is much more in peace, when developing in x86_64 to deploy on ARM I'm never sure that some weird cross-architecture bug will pop up. No matter how good my CI/CD pipeline is, it won't ever account for real-world usage.
- LoSboccacc 6y agoon the other hand, having devs an alien workstation really put stress into the application configurability and adaptability in general. it's harder in all the way you describe, but it's much more likely the software will survive migrating to the next debian/centos release unchanged. it all boils down to the temporal scale of the project.
- piva00 6y agoI'd say that on my 15 years career I had many more tickets related to bugs that I needed to troubleshoot locally than issues with migrating to a new version/release of a distro. To be honest it's been 10 years since the last time I had a major issue caused by distro migration or update.