btcd's bugs were not vulnerabilities. The specification and bitcoin core implementation has no sensible resource consumption limits on witness sizes. That's all it was. As a Go programmer, I am also very avid about keeping resources under control. It actually helps a lot with security as well. Resource exhaustion attacks can destroy peer to peer networks functionality.

Whoever is paying for development says what will get done. But the new features you speak of still work even when a minority of nodes support it, because they recognise each other as being able to and can make paths to run these new protocol API components.

Just like there is still a huge number of bitcoin nodes that still don't have segwit enabled.

We don't have to agree. This is a peer to peer system, ultimately. And LN can tolerate even more divergence than the bitcoin protocol because it's purely peer to peer.

You're free to fud and attack whoever you like but building is what gets you respect.