upvote
It's a technical forum. That's like asking to "please introduce the definition of a linker" the first time it crops up. If somebody really doesn't know, searching "aos vs soa" in Google yields a largely correct AI summary followed by a Wikipedia article on the topic followed by a StackOverflow discussion on pros/cons followed by a similar Reddit discussion. Aside from maybe the image/video results, literally everything on the first page looks like it would explain the concept well.
reply
Expanding acronyms helps bring people into your field of interest.

People who might be technical and might even intuitively understand what is meant by "Array of Structures vs Structures of Arrays" might not be familiar with the acronym AOS vs SOA, especially given SOA is already a technical acronym their brain might shortcut to, "Service Oriented Architecture", even if instantly dismissed as clearly incorrect.

By expanding the algorithm you also help let people better decide if they want to spend the time reading up more about it.

reply
It's the same problem you see with variable names though -- longer names add local clarity but give disproportionate weight to those local concepts rather than the global structure. There's value in selectively using less precise identifiers.

Maybe you agree with that and just disagree with where the line should be drawn?

reply
My line on acronyms is fairly clear, I think that introducing acronyms by expanding them on first-use is a useful guideline and principle to try to stick by.

I'd also err on the side of generally assuming that most people, even in a technical forum, don't know all acronyms unless they're very widely known outside of the topic at hand. I don't think AOS vs SOA comes anywhere close to that line.

Some acronyms are of course better understood by their acronym, I wouldn't introduce a Local Area Network (LAN), or Domain Name Resolution (DNS), so like all guidelines there's judgement to be made.

Even then, if I were writing an intro to DNS, then I would call it an Introduction to Domain Name Resolution (DNS), because it is specifically targeted as an introduction. I wouldn't do the same for SQL, because no-one calls it Structured Query Language. Fairly often it would be more confusing if they did expand it, because quite often when people talk about SQL they're not really talking about the language at all, but using it as a short-hand for talking about SQL-compatible databases, or more specifically talking about relational database management systems (RDBMS), but "SQL" is a useful shorthand to contrast to "No-SQL" databases that were popularised a decade or two ago.

reply