Linked by Thom Holwerda on Sat 9th Aug 2008 19:19 UTC
One of the common complaints regarding Microsoft is that the company has problems eating its own dog food. Even though it promoted Windows Presentation Foundation as the programming framework for building Windows and web applications, it so far failed to produce any significant WPF applications itself. None of Microsoft's major applications use WPF (Expression Design and Blend aren't major), which does not help in promoting it as the Next Big Thing. This may all change in the near future, as a small but extremely popular Microsoft application is about to make the switch to Windows Presentation Foundation: 
Thread beginning with comment 326353
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2008-03-17
Explain why people are calling it slow then?
I was under the impression that only under vista it is even somewhat hardware accelerated...
I'm slightly suspicious of you statement because you don't say it is fast due to HW Accel, you say it is HW accel hence it is fast.
As a framework how is it faster in terms of user experience?
Member since:2005-07-28
The only difference between WPF in Vista and XP is the font rendering, the rest is the same.
I don't know why some people say it is slow, the cold start is slow, after that is as fast as any other application, and even the cold start has been refined in .Net 3.5 sp1.
Edited 2008-08-10 04:26 UTC
Member since:2005-11-09
Member since:2005-11-29
Explain why people are calling it slow then?
I was under the impression that only under vista it is even somewhat hardware accelerated...
I'm slightly suspicious of you statement because you don't say it is fast due to HW Accel, you say it is HW accel hence it is fast.
As a framework how is it faster in terms of user experience?
I was under the impression that only under vista it is even somewhat hardware accelerated...
I'm slightly suspicious of you statement because you don't say it is fast due to HW Accel, you say it is HW accel hence it is fast.
As a framework how is it faster in terms of user experience?
The problem is, it's really easy to muck up performance in WPF. There's a TON of performance that can be done both in Code-Behind and in the markup language, XAML.
Having used WPF for about six-seven months I can tell you first hand, that with the great profiling tools provided by Microsoft, that anyone can improve performance.
Most importantly, you need to strike a balance. Yes, some animations will be costly, yes some effects will slow your application down to a crawl, but in the end..do you really need them? Too much of a good thing turns into a bad thing.
I've found that due to the ease of WPF (MVCish design pattern, separation of UI and logic) that it makes for GREAT Business Logic front ends.
Even if you don't use any of the effects, the amount of flexibility you gain is invaluable.
WPF not only allows you to distinguish UI from Logic. It gives you an additional power.
You can set the source binding (Logic) you can set the binding control (UI) and you can describe a template for presenting that data.
So if I have a collection that I want to add to a ListView, I can not only set it to display that data -- but I can format that data in any way I want.
WPF is a great platform, and it going more mainstream will only push Microsoft to tie any loose ends in it.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-28
WPF is fully hardware accelerated witch means is faster than WinForms, the memory is pretty much the same or better since it uses video memory.
The benefits it has for the developer are great, I've used it and is a loooot easier than WinForms and a loooooooottttt more flexible,