A rebuttal to common counterarguments against the author's position that -Werror should not be used as a default build flag. The author addresses three main objections: that -Werror problems only affect open source projects (not companies), that companies always use a single toolchain, and that capturing the build environment fully solves the problem. The author argues from experience working with dozens of companies that embedded projects routinely use multiple toolchains, update them at different cadences, and face real-world constraints that make -Werror impractical as a universal default.
