Comment

Comment by teraflop

I sort of agree but I think the issue is more subtle.

Languages change over time, and one of the well-documented "laws" of language change (using that term very fuzzily) is that people like to take irregular features of a language and generalize them to make them more regular. And there are many English verbs (particularly verbs expressing a change of state) which can be used transitively or intransitively, with equal validity:

> "I opened the door" -- "the door was opened" -- "the door opened"

> "the heat melted the ice" -- "the ice was melted" -- "the ice melted"

> "the impact cracked the glass" -- "the glass was cracked" -- "the glass cracked"

This generalization has been common, especially in jargon-y contexts, long before the rise of LLMs. A pedant might insist on saying "wait for the compiler to compile the code", and Merriam-Webster thinks "compile" can only be used transitively. But I think most developers would say "wait for the code to compile [i.e. be compiled]" is fine too. (see e.g. this XKCD comic from 2007: https://xkcd.com/303/)

In my view, this usage is completely fine as an occasional thing, especially when the social process of language change has normalized it over time for a particular verb. The issue is that LLMs drastically overuse it and pepper it everywhere. Just like "it's not X, it's Y", which is fine occasionally in human writing, but has become a dreadful cliche through overuse.

parent teraflop 7 days ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton