Hardware programmers are a fairly standard serial or SWD programmer it seems. Is there also debugging? That would make it even greater.
There is "SWD" debugging, yes. It's not the same as ARMs, you need WCH's customised OpenOCD, but the source code for their version is published (but not upstreamed). You kind of have to ask WCH for it and they easily give it to you, but (multiple by the looks) people have put it on github. The license certainly allows that. Someone needs to organise that, but yeah...
https://github.com/kprasadvnsi/riscv-openocd-wch The only disappointment for RISC-V MCU is the power consumption. 0.4 - 2.7mA sleep you got to be kidding me.
Maybe some of WCH's more pricey MCUs have better sleep. I haven't looked.
I know the GigaDevice GD32VF103 that has been shipping since 2019 (I bought a dozen Longan Nano boards for $4.90 each back then, and some bare chips from tme.eu for $1.98 each in October 2020) has "sleep", "deep sleep", "standby" modes:
sleep: 108 MHz clock: 10 mA peripherals off, 25 mA peripherals on; 2 MHz clock: 1.0 mA peripherals on, 0.7 mA peripherals off. Wake time 4.5 µs.
deep-sleep: 460 µA, wake time 6.0 µs
standby: 22 µA, wake time 118.8 ms
I believe those are reasonable compared to STM MCUs, except the wake from standby (and from power on reset is the same) is long because the program is copied from in-package (2nd die) flash into 0 wait-state SRAM for execution.
So I dunno. The sleep figures you quote for the WCH are pretty comparable. I don't know what you expect. I've never really had to deal with really conserving power like that.