1. LLM‑like prose hurts readability
Many commenters felt the article’s style read like AI‑generated text, making it hard to follow and questioning the author’s effort.
- “I get the brain scramblies [1] from trying to parse this writing style at work so I hate to see it elsewhere.” – scythmic_waves
- “The 'does not rescue it'. No human would write like that.” – kristianp (quoted by vlovich123)
- “It’s a sign that the claims in the post likely weren’t vetted very hard.” – majormajor
2. Criticism of shallow dismissals and call to follow HN guidelines
Several users argued that complaining about the writing style is a low‑effort, tangential complaint that violates the site’s rules, and that the piece contains valuable technical content worth reading whole.
- “Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.” – gchamonlive (quoting the HN guidelines)
- “If you disagree with the article style, there is a flag button there.” – gchamonlive
- “Just read the damn post, it's very good, there's nothing low effort…” – gchamonlive
3. Appreciation of the technical insights and visualizations
Despite the style debate, many praised the visualizations, the new C++ extension API, and deeper technical points such as parallelism and recursive‑CTE optimisations.
- “Great visualization. Side note their new c++ extension api is also gonna be faster from the perspective of development / distribution of those extensions.” – stacktraceyo
- “I wish more database engines used a Task‑based design like Umbra / CedarDB.” – jiggawatts
- “The section on recursive CTEs wasn't well written… This article explains how the recursive CTEs were improved …” – kristianp (linking to a follow‑up post)