analogWrite may sound like a nice intuitive name but its not really very helpful because its behaviour appears odd to people that don't understand why only certain pins can be used, and only if some other library is not using them, and with values that have a different range from analogRead.
I have seen many non-technical people come unstuck when introduced to analogWrite because they expect it to be similar to analogRead - in the same way as digitalWrite is similar to digitalRead.
Guess I am in the minority on this but as a non-engineer I think 'analogWrite' is appropriate. Here's why I think this:
digital = on/off - binary
analog = range/continuous
True, analogWrite might be more accurately named simulationOfAnalogOutput
but that is not necessary for the less technical user to understand, at least at first. PWM is the way this simulation is achieved/implemented. The PWM pins available, etc. I see as simply FOL details with specific boards.
I guess I see analogWrite in the same way as setup & loop - simplifications/higher level abstractions that are easier for new users/less technical people to grasp.
No matter - just thought I would offer this POV.