Staffing Talk » Technology » Time To Discredit The WPF Naysayers

Time To Discredit The WPF Naysayers

Written by

November 7, 2007

Great is not the enemy of good.

I don’t like to spend a lot of time discrediting competitors, but I’ll make an exception here because of the PR traction one has gotten with a well-written (but faulty) blog post that criticized WPF.

Briefly, WPF encompasses Microsoft’s next generation Windows platform, which TempWorks uses for its Enterprise product line. WPF is in fact very new, and we are the only company I’m aware of offering a Microsoft Certified line-of-business application. Its advantages to the user community begin with the ease of use and extend to compatibiltiy with different device types.

But, I digress.

Here is the critic’s post. He nuances his arguments with a lot of true statements. The WPF programming tools have in fact been difficult to use, and WPF itself, with dependency properties and a host of new object classes, certainly poses its challenges to programmers.

But, his primary thesis that you can’t build good WPF products and should stick with older development platforms suffers from an obvious problem: If it’s not possible, then how did we do it?

Not just TempWorks, but a host of other companies (like Netflix, Yahoo and NYTimes) have built incredible WPF applications and have them in production.

Mr. Ward, in my opinion, may be suffering from denial. I don’t know him, but he shows the signs of living in the fantasy world of the last platform that he happened to become proficient in and just can’t get it up anymore. If alpha development tools make a platform “unfit for use” as he suggests, then let’s get rid of all of the software developed in the last 25 years and go back to using Assembler like God intended.

Hmmph!

Fortunately, great is not the enemy of good, and WPF is here and doing well. Give TempWorks Enterprise a try if you have any doubt!

Leave a Comment

Notify me of followup comments via e-mail. You can also subscribe without commenting.

Previous post:

Next post: