WPF Sucks!
-
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
-
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
1. Animation is a pain, learning the ropes more each day.
Software Kinetics - Moving software
-
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
Rama Krishna Vavilala wrote:
4. Does not work everywhere properly aka Remote Desktops.
That. ...Is a show-stopper for me. I've played with WPF briefly for a couple of personal, toy projects, but any desktop UIs i do for work must function over Citrix / Net Meeting / Remote Desktop.
-
Rama Krishna Vavilala wrote:
4. Does not work everywhere properly aka Remote Desktops.
That. ...Is a show-stopper for me. I've played with WPF briefly for a couple of personal, toy projects, but any desktop UIs i do for work must function over Citrix / Net Meeting / Remote Desktop.
The whole problem is that it sometimes works and for apparently no reason it does not some other times. Of course the perf is pretty bad on RD.
-
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
-
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
This post is kind of pointless - but just wanted to say I'm glad you're trying to get a balanced view. I played with WPF when it first came out (in VS and Blend) and thought cool! Then I tried to do a real world utility app in it and after a few days of pulling my hair out I gave up as I could have finished it long ago in WinForms. If it is really the way we're going, then I'm quite happy to put in the time learning, but I've yet to be convinced that it's going to be here to stay and not dropped like a MS fad. I've followed the various posts over the last few weeks (silently) with great interest, and I'm hoping the way you've posed both your questions will bring out the real answers.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)
Why are you using VB6? Do you hate yourself? (Christian Graus) -
The whole problem is that it sometimes works and for apparently no reason it does not some other times. Of course the perf is pretty bad on RD.
If I understand it correctly, the problem is that the original plan was to allow for a more efficient means of remote drawing (than simply rendering to a bitmap server-side and sending it across) when both client and server supported it... But it never really got tested/refined properly and was eventually dropped. I'm still holding out hope that this will all be working properly somewhere down the line (.NET 4 + We7en perhaps?). It sounds great, in theory. But everything i had hoped to use it for is well under development now, so...
-
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
It would be easier to say why it doesn't suck because there are far fewer reasons that it doesn't: 1) When I take a dump, I can do it without the IDE crashing on me. 2) I don't need WPF to sleep or eat. 3) My wife doesn't care about WPF. 4) My dogs still love me, even though I write WPF apps.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
Why are people choosing WPF in the first place? What is selling them on it? Some specific demos? Promises of a better tomorrow :rolleyes:?
Todd Smith
-
It would be easier to say why it doesn't suck because there are far fewer reasons that it doesn't: 1) When I take a dump, I can do it without the IDE crashing on me. 2) I don't need WPF to sleep or eat. 3) My wife doesn't care about WPF. 4) My dogs still love me, even though I write WPF apps.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001You forgot "0)". What's up with that?
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Oh
-
Why are people choosing WPF in the first place? What is selling them on it? Some specific demos? Promises of a better tomorrow :rolleyes:?
Todd Smith
Shiny things. Gradients. All the cool kids are using it. Oh, yeah, I almost forgot, data-binding (which is admittedly really nice).
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Oh
-
Why are people choosing WPF in the first place? What is selling them on it? Some specific demos? Promises of a better tomorrow :rolleyes:?
Todd Smith
-
You forgot "0)". What's up with that?
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Oh
No, he didn't, it was supposed to be rendered using WPF, but ... well ... you get the idea ...
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
-
Rama Krishna Vavilala wrote:
4. Does not work everywhere properly aka Remote Desktops.
That. ...Is a show-stopper for me. I've played with WPF briefly for a couple of personal, toy projects, but any desktop UIs i do for work must function over Citrix / Net Meeting / Remote Desktop.
Reminds me of some early implementations of X-Windows on Unix. You'd move your mouse all around the screen and bring the network to it's knees as a several thousand mouse-move messages went down the wire for the server to process. :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
-
No, he didn't, it was supposed to be rendered using WPF, but ... well ... you get the idea ...
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTLPrecisely - it's a databinding quirk in WPF...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
That the promised multithreading support did not make it to production was a shame. But the show stopper for me is the weak typing. The compiler cannot verify the magic strings in XAML which, having earned my spurs in Ada, seems like a step back to the stone ages to me. Nick
---------------------------------- Be excellent to each other :)
-
No, he didn't, it was supposed to be rendered using WPF, but ... well ... you get the idea ...
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL:laugh:
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Why are people choosing WPF in the first place? What is selling them on it? Some specific demos? Promises of a better tomorrow :rolleyes:?
Todd Smith
It was a corporate mandate, not a personal choice on my part.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
Ok this is the my second post on this topic as people are using my WPF Rocks! to post their rants. My aim is to get the good and the bad of WPFs. Why do you think WPF sucks? Here are my reasons:- 1. Of course it's no doubt that the top one would be the poor VS 2008 designer. (Again please don't post that the problems will be solved by Expression Blend that's not the point of this post), 2. XAML is verbose. 3. Poor performance. 4. Does not work everywhere properly aka Remote Desktops. Anything else?
Admittedly, I have had little time and experience with WPF, however, I can list out the "suckage" I have encountered, in my short time with it: 0). Large XAML Windows, Controls, etc... crash VS without so much as an error message. I have this happen on two different machines, with various projects. I'd love to report it, but since I have no error message, well ... 1). Complex XAML won't even render in the VS editor; if it opens without crashing. 2). Slow. Slow slow slow slow slow. It's freak'in S-L-O-W in the IDE, slow outside the IDE, and even typing text in some of the controls renders ... SLOW. Ok, I've totally just killed that word, it's lost all meaning now. Frankly, it's so bad, what little WPF I have done, I do manually outside the IDE. 3). Build a WPF solution with no errors. Close studio, come back to that same solution, having no files changed in the solution what-so-ever. Run. Get dozens of XAML related namespace not found errors. The only "fix" is to rebuild the entire solution. Makes me want to stab myself in the forehead with a spork to relieve the pain in my brain that this causes; my company will no longer let me near the plastic utensils because of this. 4). Intellisense. Oh ... wait ... sorry ... there is none for XAML files. What they've done to us, is what drug dealers do: get us all hooked on using something, and then take it away. But unfortunately, there are no street vendors I can shell a bunch of money out to that can give me a FIX! Ok, now my eye's twitching. That's all I've got, it's making my brain hurt ... someone ... hand me a spork.
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL
