The article argues that programming languages should be customizable rather than fixed artifacts, and that historical objections to macros and language modification—primarily concerns about code readability and maintainability—are less valid today given modern tools and practices for understanding code.
A programming language design post discusses the complexity of implementing type system features that reason about aliasing, specifically in-place updates in Futhark. The author explains how tracking object identity and aliases through the type checker creates non-trivial design challenges when interacting with other language features, and recommends avoiding such complexity unless absolutely necessary.