Re:Ask HN: How do you write Windows desktop software these d...
by brudgers on Tuesday July 31, 2012 @10:01AM
(#4317249)
When committing long term to Windows Desktop development, why would one choose the learning curve of a framework outside the Microsoft toolchain? It seems to me that choosing a multiplatform tool chain for Windows development is somewhat likely to be premature optimization (most things be equal).
I'd add that unless there is a compelling set of legacy code, win32 and MFC are not really serious options to .NET.
On the other hand, forms is an option to WFC for a minimum viable product - but not once UX design rises in importance. Early on, I would say that WFC v. Forms is purely down to investment in the learning curve.
I'd add that unless there is a compelling set of legacy code, win32 and MFC are not really serious options to .NET.
On the other hand, forms is an option to WFC for a minimum viable product - but not once UX design rises in importance. Early on, I would say that WFC v. Forms is purely down to investment in the learning curve.