+ AA6YQ comments below
Well, I think there are lots of advantages of moving to IPv6.... but mostly from a large enterprise perspective. For example, large enterprises are running out of RFC-1918 addresses. Interoperability is a pain. For example, when two companies merge, they most likely have overlapping address space, which causes one part of the company to renumber or install translation mechanisms. So IPv6 is a great option because you can solve these problems with unique IP address space. Note - running an IPv6 network and an IPv4 network essentially means you're running two networks. So ditching IPv4 lets you get back to running a single network.
+ Based on this Microsoft document
+ support for IPv6 would require updating each DXLab application to switch from one set of Microsoft network components to another, and to enable users to specify the much larger IP addresses required by IPv6. None of this is likely rocket science, but the testing and tuning efforts alone would be significant, especially for a performance-sensitive application like SpotCollector. Since as you point out IPv6 provides no benefit to the typical ham, spending time on an IPv6 update instead of on the many other tasks on the enhancement lists cannot be justified.
+ Note that I do not publish a Roadmap for DXLab. What I publish are my priorities:
1. answering questions
Hopefully, this doesn't start some sort of long string of e-mails. I'm just asking the question because I didn't know.+ Your question was entirely appropriate. Whenever someone poses a question about something not on my radar, I consider it as an opportunity to be educated.