> and was generally more flexible and extensible Depends on the direction where you’re extending them. I’ve extended both WPF and XAML with 3D rendered conten

> and was generally more flexible and extensible Depends on the direction where you’re extending them. I’ve extended both WPF and XAML with 3D rendered content. WPF still uses Direct3D 9 under the hood. Interop with modern D3D took some time to implement and debug: DXGI surface sharing is complicated, I remember hunting several bugs related to lost devices and concurrency. Win8/XAML already uses Direct3D 11; interop with custom 3D content is painless, I don’t recall any issues.