sudahtigabulan

> Note that programs were usually typed on as few lines as possible, because they had to be punched to punched cards or typed in at a teletype which echoed its input on paper.

I suspect this is the real reason behind "cram all the closing parentheses together on the same line" rule.

The only rationale I've seen online is in Taylor Campbell's style guide:

> Absolutely do not place closing brackets on their own lines.

> ...

> Rationale: The parentheses grow lonely if their closing brackets are all kept separated and segregated.

Yeah, right.

Anybody know anything about how this rule came to be?

This setting is "Always relay calls", and the only difference it makes is for already established calls. Messages and calls setup always go through Signal's servers.

> The P/B distinction will be difficult for many people as well.

P/V/F confusion is also a thing, in Indonesia.

V and F tend to be pronounced as P. And if you pronounce the letter "correctly", some Indonesians might not recognize the word. They've never heard it this way.

When you can only see half of a car, the red turn signal lights also make it impossible to tell quickly whether the car is about to get into your lane or the driver's foot is on the brakes.

This situation can happen both in traffic or in a row of parked vehicles.

> Wtf kind of intro to a programming language doesn’t include syntax rules?

PP could have been more clear and say syntax-rules (note the dash), which means macros. Macros are usually considered an advanced topic.

There is a naming tradition in the Lisp world, which Racket devs apparently have chosen over searchability.

Qualities or activities that have negative connotations. Guile. Gauche. Larceny. Racket.

I think it started with theorem provers - Planner, Conniver. Then Scheme[r].