GoKawiilEssay argues programming languages should be user-customizable, not fixed
A new opinion piece contends that programming languages are treated as fixed, sacred artifacts, forcing developers to build workaround build systems and conventions instead of directly modifying their languages. It cites Raymond Chen's 2005 blog post opposing 'flow-control macros,' which warned that such customizations obscure code semantics and complicate debugging, as an example of the resistance to language malleability.
GoKawiil's interpretation of the reporting above, not reported fact.
The piece suggests that current tooling culture undervalues customizable languages, which could be limiting how flexible and expressive codebases can become. By highlighting Chen's decades-old counterargument, the author implies that longstanding fears about readability and debugging have shaped industry norms more than technical necessity, though this remains the author's interpretation rather than settled consensus.
- The essay critiques the industry norm of treating programming languages as unchangeable.
- It references Raymond Chen's 2005 argument against flow-control macros as a key historical objection.
- The core tension raised is between customization flexibility and code readability/debuggability.
Source: jimmyhmiller.com, 2026-09-25
Published there as: “We Should Be Able to Change Our Languages”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.