If the name were an arbitrary word which didn't attempt to define itself, would that be any better? I don't see why the name must mean anything specific, nor why you should expect the name to explain what the project is. That's what the documentation or other descriptive text is for. That the name gives some understanding at first glance is a bonus.
PnR is "place and route", and is a very common acronym in the ASIC/FPGA/VLSI space. It seems fair to expect those who'd use this specialized variant of Yosys to also be familiar with PnR. For reference, here's [1] Yosys's PnR tool, which expands the acronym in its README title.
Realistically, if you're using Yosys tools, you're going to need to have some familiarity with the underlying flows anyway; in my experience they're very powerful but also pretty DIY. That's not great, but it's the reality. That's just the nature of the space right now, given the alternative is a ~$1M single user license.
PnR is "place and route", and is a very common acronym in the ASIC/FPGA/VLSI space. It seems fair to expect those who'd use this specialized variant of Yosys to also be familiar with PnR. For reference, here's [1] Yosys's PnR tool, which expands the acronym in its README title.
Realistically, if you're using Yosys tools, you're going to need to have some familiarity with the underlying flows anyway; in my experience they're very powerful but also pretty DIY. That's not great, but it's the reality. That's just the nature of the space right now, given the alternative is a ~$1M single user license.
[1] https://github.com/YosysHQ/nextpnr