How do you use "future proof" and "avrdude" in the same sentence and keep a straight face?
avrdude is and has been a nearly unmitigated disaster nearly as long as I have been using Arduino (which I think was around when the guy bailed) the only mitigation has been a handful of patches practically forced onto the Arduino folks (or, in one of those rare cases where shit rolls uphill, apparent,y someone from Microchip) because of the scope and severity of it's impact......What was the last count of open, untriaged issues on their bug tracker? Was it still in 4 digits or has it hit 5 by now?
Seeing as nobody has been doing more than base minimum gun--to-head maintenance on it for years, and that it hasn't been properly maintained at any point in time since it's creation, avrdude doesn't seem like a good horse to hitch your cart to. If it weren't for some problem with installling the python USB dependancies via board manager or something (that's Quentin's department not mine, and I never kneew what the issue was, just that he suddenly got all pessimistic when I suggested it), I would be calling out to pymcuprog not avrdude to upload via the Microchip programmers.
I have also wished badly that I had the time to implement STK500 and the other protocols people care about in a python program..... a good fraction of the problem with avrdude is just plain kitchensinkism. (far from the only problem but.....)