News for hackers. Stuff that matters.
Re:Inside the M4 Apple Neural Engine, Part 1: Reverse Engine... by tzs on Monday March 02, 2026 @02:39PM (#47223014)
Below are the items from that section. How should they be written to not look like an AI?

> hollance/neural-engine — Matthijs Hollemans’ comprehensive community documentation of ANE behavior, performance characteristics, and supported operations. The single best existing resource on ANE.

> mdaiter/ane — Early reverse engineering with working Python and Objective-C samples, documenting the ANECompiler framework and IOKit dispatch.

> eiln/ane — A reverse-engineered Linux driver for ANE (Asahi Linux project), providing insight into the kernel-level interface.

> apple/ml-ane-transformers — Apple’s own reference implementation of transformers optimized for ANE, confirming design patterns like channel-first layout and 1×1 conv preference.

Re:Inside the M4 Apple Neural Engine, Part 1: Reverse Engine... by qaadika on Monday March 02, 2026 @11:59PM (#47228282)
The grammatical structure in the middle two is identical, and they're all similar in that way.

- "- Name - {Noun with modifiers} {comma} {verb-ing with modifiers}."

- "- Name - {Noun with modifiers} {comma} {verb-ing with modifiers}."

The phrasing is the same, which I notice sometimes happens in my own notes, but it's most noticeable when an LLM is asked to summarize items. An AI written job description (without major prompting) for a resume comes out the same way, in my experience. It's the simplest grammar for describing what something is and what something does.

If we used the developer's descriptions (from the github repo) to populate the info, it would look like this:

- hollance/neural-engine - Everything we actually know about the Apple Neural Engine (ANE)

- mdaiter/ane - Reverse engineered the Apple Neural Engine, with working Python and Objective C samples

- apple/ml-ane-transformers - eiln/ane - Reverse engineered Linux driver for the Apple Neural Engine (ANE).

- apple/ml-ane-transformers - Reference implementation of the Transformer architecture optimized for Apple Neural Engine (ANE)

IMO It may not be as information-packed as the LLM list, but it is more interesting to read. I can tell, or at least think I can tell, that different individuals wrote each description, and it's what they wanted me to know most about their project.

If I were making a list of software during research, the particular details I write down in the moment would be different, depending on the solution I'm looking for or features it has. I don't try to summarize "the Whole Project" in one point, i can re-read the repo for that. But overall, unless I made an effort to normalize the list, the grammar, length, and subpoints would vary from the form-identifiable "LLM Concise Summary."

EDIT: upon re-reading the article, I noticed the "Prior Art" section is written in past-tense, as I would expect. But the list is in present tense. I feel like it jumps from "narrative" to "technical details list" back to "narrative". And the list is 70% of the section! I wouldn't mind reading a whole paragraph describing each project, what worked, what didn't, what they could use and what they couldn't, in the past tense, if it were interestingly-written. Something that tells me the author dove into the previous projects, or spoke to their developers. Or even if they disagreed with the approach. but "interestingly-written" isn't really the LLMs goal, nor its ability. It's maximal information transfers with minimal word count.

Re:Inside the M4 Apple Neural Engine, Part 1: Reverse Engine... by leoedin on Tuesday March 03, 2026 @10:28AM (#47233843)
The AI-ism that annoys me the most is the unnecessary hubris. Just sampling a small portion of the linked article:

"Here’s the fascinating part:", "And one delightful discovery: "

Personally I find the AI-isms take away from the voice of the author. What does the author find interesting? What was their motivation? It's all lost in a sea of hubris and platitudes.

There's almost certainly a positive side - technical people who aren't so good at communication can now write punchy deep-tech blogs. But what's lost is the unique human voice that is normally in every piece of writing. It's like every blog is rewritten by a committee of copywriters before it's published. Bleurgh.