This issue seems to mostly be (healthy) debate on that "can you port legacy app x to new stack y" front. It should (eventually) resolve to most people's satisfaction, but the sausage is being made in public on GitHub and that's new and frightening to some .NET veterans.
«Can / should I still use WPF? Did it secretly continue under a different name?»
You can still use WPF if you are happy with it. The Universal Windows Platform (UWP)'s .NET/XAML stack is the relatively open and acknowledged successor to WPF. It should be quite familiar to existing WPF developers and offers some nice new features and performance. Porting to UWP is still sometimes tough from WPF, but Project Centennial/the Desktop Bridge can make it a lot easier to do the transition a piece at a time.
«Can / should I still use WPF? Did it secretly continue under a different name?»
You can still use WPF if you are happy with it. The Universal Windows Platform (UWP)'s .NET/XAML stack is the relatively open and acknowledged successor to WPF. It should be quite familiar to existing WPF developers and offers some nice new features and performance. Porting to UWP is still sometimes tough from WPF, but Project Centennial/the Desktop Bridge can make it a lot easier to do the transition a piece at a time.