--- title: "Responses to the Commentariat on the -Werror Article" url: https://daily.dev/posts/responses-to-the-commentariat-on-the--werror-article-s1jtln8xm source_url: https://embeddedartistry.com/blog/2023/10/27/responses-to-the-commentariat-on-the-werror-article type: article source: "Embedded Artistry" published: 2026-05-31T07:47:22.573Z updated: 2026-05-31T08:47:43.578Z tags: ["embedded", "build-systems"] reading_time: 6 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Responses to the Commentariat on the -Werror Article **[Embedded Artistry](https://daily.dev/sources/embedded-artistry)** · 6 min read · 0 upvotes · 0 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [On C extensions, portability, and alternative compilers](https://daily.dev/posts/on-c-extensions-portability-and-alternative-compilers-xh1x5m5qq) · Hacker News · 0 upvotes · 0 comments --- Tags: [#embedded](https://daily.dev/tags/embedded), [#build-systems](https://daily.dev/tags/build-systems) [View this post on daily.dev](https://daily.dev/posts/responses-to-the-commentariat-on-the--werror-article-s1jtln8xm)