

Yes, but I am also of the opinion that not one single acronym should be used without at least once in the section saying what the acronym is. Many many programing docs with say what am acronym is exactly once, somewhere in the docs, and then never again.
Also, if there are more complex concepts that they use that they don’t explain, a link to a good explanation of what it is (so one doesn’t have to sift through mountains of crap to find out what the hell it does). Archwiki docs do this very well. Every page is literally full of links so you can almost always brush up on the concepts if you are unfamiliar.
There seem to be 10 extremely low quality, badly written, low effort docs for every 1 good documentation center out there. It is hard to RTFM when the manual skips 90% of the library and gives an auto-generated api reference with no or cryptic explanations on parameters, for example.







It is funny because electric motors have nearly unlimited* torque depending on the kind. If you have thick enough power cables and winding conductors, you can just keep pushing it harder to get more torque.
It is like the thing they are very good at, besides sound levels, double or triple the efficiency, low/no maintenance, simpler with less parts, no emissions, etc…
Literally the only good thing about combustion engines are their fuel source energy density.
I think the problem is that motorheads see the enshittification of the auto industry as a whole and just say it’s because of electric motors because it happened right about the same time as EVs started coming out and try to push back on the wrong thing.