> porting a browser to RISC-V Modern web browsers take several hours to compile on reasonably powerful hardware. (I don't know much about rebuilding for increm

> porting a browser to RISC-V Modern web browsers take several hours to compile on reasonably powerful hardware. (I don't know much about rebuilding for incremental changes. TBH I'm terrified of the scope to even try.) Also that sounds like an incredibly niche application? > [...] as they don't then need to find another spare power cable and a spare monitor to connect to an SBC. My own solution is to use an HDMI capture stick to display a window on my main workstation. Works great for kiosk-type applications, and I keep my regular setup for actual coding. I previously used the hardware PIP feature of my monitor, but it will often obscure another window. If I need KVM, and for devices that support that, I have a screen that does USB-C with DP, plus an internal USB hub to connect the keyboard and mouse. One cable to rule them all. I could probably get half a dozen USB-C/DP into HDMI+USB-A adapters but honestly swapping two cables instead of one is not that big of a deal. My screen has 4 HDMI inputs, regular DP, and USB-C/DP. I ended up using all of them ;) Plus you get to pick more powerful HW to actually support development - even a 20% improvement is big, and IIRC that was the difference between Jetson T210 and RasPi4; enough to do non-Jetson-specific builds on a different board.