I was also confused by the lack of focus on the article. It felt like it was an article of two halves: 1. An example of the how printing isn’t simple and how d

I was also confused by the lack of focus on the article. It felt like it was an article of two halves: 1. An example of the how printing isn’t simple and how different languages hide that complexity in different places (though even there it gets weirdly hung up on the difference between “scripting” and systems languages despite the examples clearly showing the same kind of abstractions hiding the same kind of complexities) 2. A low level dive into the Zig programming language. This felt more like promo piece, which is perfectly fine, but where the article stated it’s not about Zig specifically is clearly a misrepresentation when more than 50% of the article specifically covered the Zig compiler. I think this would have made more sense as two articles. One as a high level overview of how different languages handle builtins / core libraries like ‘println’, and another that is unashamedly a Zig promo piece (and there isn’t any shame in promo pieces here because languages that aren’t sponsored by big corps need such articles to garner developer interest).