judge2020 5 hours ago

Were semicolons in subheadings common before AI? This subheading of the TomsHardware article just seems very artificial:

> The fingerprint only switched the USB connection on; nothing on the card was encrypted.

▲

solyin 5 hours ago | parent | next [-]

Oh god dammit, I have to stop using semicolons now? That's stupid.

	▲	judge2020 4 hours ago \| parent [-]
		Less semicolons overall, more the "statement; reveal/impact" formula that current frontier models like.

▲

weego 4 hours ago | parent | prev | next [-]

They were if you read a news source that catered to literate readers.

▲

swinglock 5 hours ago | parent | prev | next [-]

Not long ago it would have been an em dash.

▲

Loughla 5 hours ago | parent | prev [-]

I mean, it's a terrible subheading because it's way too long, but it's grammatically correct. It doesn't read like AI to me, why do you think it is?

▲

pdpi 5 hours ago | parent [-]

The issue with AI-produced text is rarely bad grammar these days (if anything, that's a marker of human-written text now!), but rather stiff-sounding constructions that humans don't actually use. In this case — semicolons are grammatically correct, but very few people actually use them them (same for em-dashes like what I just used, but you can pry them from my cold, dead fingers).

	▲	Loughla 2 hours ago \| parent \| next [-]
		I absolutely use semicolons when writing professionally. They're just basic parts of grammar, and if you want to be taken seriously by some parts of the world (academia, I'm glaring angrily at you), you would use them. I guess it comes down to expectations? You don't expect formal conventions from a website writer, while I absolutely do. I find it interesting that it was a flag for AI writing for you. That's going to make me consider my voice in certain situations now.
	▲	robertoandred 3 hours ago \| parent \| prev [-]
		I’d expect people writing for a living to understand and use semicolons.