I cant get a conversation started here. I actually came here to get a couple question answered , maybe make a suggestion or two, what do I find ,more WPF FUD , its has been going on for years, I let it go in the past, I never confronted Scott Barnes directly or complained to anyone other than friends, I didn't complain when MS push a .Net update that ruined my WPF performance , 2 days after build 2011. I have endured customers telling me WPF is obsolete, I didn't complain, customer hate that anyway, I didn't complain about the transparent undermining of WPF at every turn by Dev Div , oh sorry didn't have time for WPF solution, so busy, and so excited!!! oh look lightswitch can do what WPF can, sigh. said nothing, oh look Wn8 has ruin DWM aero disable but DWM always on (wouldn't want some one to work around DWM for proper WPF), tried to reason with sinoffski (just kidding,LOL). I wont bother going further you get the Idea, so have I made the mistake engaging people making provocative statements from clearly uninformed people like the guy who wants native WPF, like that will fix performance problems when the WPF render thread is already a Native thread and with the unpredictable lifetime of WPF object is sure to cause memory leaks with little or no improvement in speed, or the slow griders, do you have to explain to every one of them about virtualization? like a nuanced explanation wouldn't just get them flaming harder or just sit back and watch while they drive the reputation of WPf into the Mud? so I've drawn a line in the mud as far as C#/.net/WPF , anyone inside or out of mcrosoft, talk smack about WPF on the .Net , should be ready to back it up, I am, with code if need be for example.
which is wrong, and was parroted by the Register, the WPF is DEAD is fine, WPF is DEAD , long live WPF! but the faux experts with their fabricated facts are going to hear from me if I see it!
I't easy to see why some might think WPF is somehow deeply flawed when people like that Register guy is tweeting "#WPF touch may never work", and looking at the way visual studio team hasn't been able to master WPF themes, and is using blurry bitmap icons which are useless on HiDPI screen, I can almost hear the behind the scene(lets just port VS to Universal, and unify the cloud/offline UX", why shouldn't I suspect there will be more underhandedness from Dev Div, after all we don't want friction for next generation of universal apps! so can't help but wonder if I'm dealing with a vendor or an hostile enemy. I also wonder if this is even the right forum to discuss any real issues at all, If we propose an good Idea will it end up in xamarin not WPF, what is xamarins connection to this site at all, it's not .Net core, yet every other post has xamarin content, yet I saw a guy get a post with a link to his product get hidden. if it's ok to xamarin which is not free/open source or .Net core, what exactly are the guidlines for third party frameworks like xamarin?
If you don't answer any thing else please, what about WCF/MEF core or not?