it's not only the size - it was pushed all at once, anonymously, using text that highly resembles that of an AI. I still think that some of the text is AI generated. perhaps not the code, but the wording of the text just reeks of AI
For some of my projects I develop against my own private git server, then when I'm ready to go public, create a new git repo with a fully squashed history. My early commits are basically all `git commit -m "added stuff"`
The repetitiveness of the shell commands (and using zig build-exe instead of zig run when the samples consist of short snippets), the filler bullet points and section organization that fail to convey any actual conceptual structure.
And ultimately throughout the book the general style of thought processes lacks any of the zig community’s cultural anachronisms.
If you take a look at the repository you’ll also notice baffling tech choices not justified by the author that runs counter against the zig ethos.
(Edit: the build system chapter is an even worse offender in meaningless cognitively-cluttering headings and flowcharts, it’s almost certainly entirely hallucinated, there is just an absurd degree of unziglikeness everywhere: https://www.zigbook.net/chapters/26__build-system-advanced-t... -- What’s with the completely irrelevant flowchart of building the zig compliler? What even is the point of module-graph.txt? And icing on the cake in the “Vendoring vs Registry Dependencies” section.)
trenchpilgrim|3 months ago
For some of my projects I develop against my own private git server, then when I'm ready to go public, create a new git repo with a fully squashed history. My early commits are basically all `git commit -m "added stuff"`
BlackjackCF|3 months ago
wild_egg|3 months ago
> Learning Zig is not just about adding a language to your resume. It is about fundamentally changing how you think about software.
The "it's not X, it's Y" phrasing screams LLM these days
xeonmc|3 months ago
The repetitiveness of the shell commands (and using zig build-exe instead of zig run when the samples consist of short snippets), the filler bullet points and section organization that fail to convey any actual conceptual structure. And ultimately throughout the book the general style of thought processes lacks any of the zig community’s cultural anachronisms.
If you take a look at the repository you’ll also notice baffling tech choices not justified by the author that runs counter against the zig ethos.
(Edit: the build system chapter is an even worse offender in meaningless cognitively-cluttering headings and flowcharts, it’s almost certainly entirely hallucinated, there is just an absurd degree of unziglikeness everywhere: https://www.zigbook.net/chapters/26__build-system-advanced-t... -- What’s with the completely irrelevant flowchart of building the zig compliler? What even is the point of module-graph.txt? And icing on the cake in the “Vendoring vs Registry Dependencies” section.)
dilap|3 months ago
E.g., "Zig takes a different path. It reveals complexity—and then gives you the tools to master it."
If we had a reliable oracle, I would happily bet a $K on significant LLM authorship.