The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
One guy I know has bought a WiFi cat feeder?, I mean cats are nature's little serial killers and it sounds like a device that will have little support and turn into a security hazard, mind you he has a smart home hosted by a Chinese company?
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
Seriously I don't quite understand the anti-WPF crowd.
To be fair, if I reminisce back to 2005, I think I did find it kind of over complicated and bloated at the time...
But since then I came to love it far above all other GUI toolkit.
I suspect most WPF tutorial and introduction are totally lost in power user considerations.... WPF is best by far. And by best I do mean it's also the simplest, believe it or not!
I tried to write the introduction than it deserve once... (and unexpectedly won an award for it), have a look!
Well... I never used the designer... At least never used to build my UI, sometimes (often?) used it to preview the UI.. but always directly writing the Xaml. The designer should be renamed "Previewer" would work better!
I too prefer C# over XAML.
However some of the things that Xaml do just CANNOT be written in C# (attached property and markup extensions come to mind), once I accepted that, and took advantage of Visual Studio code completion / intellisense (such as automatically renaming end tag and closing tag) I got over it.