News for hackers. Stuff that matters.
Re:How to Write in Plain English by MaxBarraclough on Tuesday August 25, 2020 @01:49PM (#24273963)
> If I were to do this, my paragraphs would become at least 3 times as long. Because much of my writing

I find this jarring to read. That should be a comma, not a period. By using a period, you've technically made your sentence shorter, but the structure is unchanged. Alternatively you could just chop the Because, and it would flow fine. I really doubt your writing is thrice the density of mine. I very rarely encounter writing that approaches sentences this way, authors are able to get by fine without it.

I find it similarly jarring to read the sentences beginning with and, or but. It's as if you've told me the sentence is finished, only to then reopen it. It's like a programming language permitting a && b; && c;

There may be situations where it's ok to do this, but I wouldn't overuse it.

Re:How to Write in Plain English by rocqua on Wednesday August 26, 2020 @10:06AM (#24282595)
> Alternatively you could just chop the Because, and it would flow fine.

Hmmm, I guess I agree. I am going to try that a lot. In sentence structure I often get the issue of "$Claim, because $justification." This leads to really long sentences that I feel should be split. And again, I want to preserve the link between the two parts. Doing $Claim. $Justification. Feels like I am making an unsubstantiated claim followed by another unrelated claim.

In the programming language I would see this sort of as:

    int a = foo(b);

    int foo(b){
        return 1 + b
    }
(Ignoring a forward declaration of foo in some header).

I guess this is similar to my earlier point. Where I want to split the un-related parts but still want to capture the strong relation between the two.

An alternative might be something like.

"We know that $justification. Hence, it follows that $claim."

You've given me food for thought. Thanks!