This looks as opprotunity for more innovation. It may happen that all three approaches will be embraced - write new code for critical apps, device auto convert utilites for some predictable code and change code manually.
The author has made a very valid point, which comes at the problem from a different point of view, but points at the same disaster, running out of memory and crashing to a halt. As Mr Anderson points out, memory is a big deal, and it is far from infinite. While I don't understand fully the differences between IPV4 and IPV6, his point about the memory problems is certainly valid enough to make one ask "is this really a good idea?" And the prospect of programs just continuing to allot memory space and then not release it does certainly describe a very real and very fatal fault in a lot of current code. And the description of the effort needed to make changes is sort of depressing, I think.
As we unveil EE Times’ 2015 Silicon 60 list, journalist & Silicon 60 researcher Peter Clarke hosts a conversation on startups in the electronics industry. Panelists Dan Armbrust (investment firm Silicon Catalyst), Andrew Kau (venture capital firm Walden International), and Stan Boland (successful serial entrepreneur, former CEO of Neul, Icera) join in the live debate.