WPF ? more like WTF

@rEaL-jAsE exactly.
good because demanding skillset

Bad because What the fuck. (Coming from an Android dev background be like) in android I used Java and XML

But I'm WPF is C# and Xaml.

Learning this because applying a job in Intel. They need this skill so...

@rEaL-jAsE thanks

@rEaL-jAsE yea. Personally I still prefer QT5 with C++ ,

We're heavily invested in the WPF platform and the framework allows for some unbelievably complex ways to do very simple things. I swear it seems there were teams who fought over how difficult they could show data to a user.

Playing around with Blazor, I replicated a user-control and one the WPF devs looking at the code was like

Dev: "Where are the converters? What about the data templates? Where are the event listeners defined? Are the ICommand implementations thread safe?"

Good grief, what happened to simplicity? MS really dropped the ball by allowing code-addicts to get their drug fix with that nonsense. What happened to "If you're writing a lot of code to do something, you're probably doing it wrong." MVVM pattern...looking at you.

@PaperTrail what's your opinion on blazor so far? Would you use it for a real application?

WPF kinda do be my favorite desktop development library doe

But yeah, it's kinda ridiculous in some aspects. But honest to God, it's pretty nice sometimes and its children (UWP, WinUI 3) have lots to learn from it.

FUCK UWP.

I worked with winforms and wpf, and in the begin I liked the simplicity of winforms but needed wpf for the hardware accelerated rendering.

However now I know how it all works I fully switched and will never make something in winforms ever again.

@ars1 > "what's your opinion on blazor so far? Would you use it for a real application?"

As of now, absolutely. I haven't ran into any "can't get there from here" situations yet, but my experience has been very rudimentary. My issues with Blazor has been 'tiny cuts', not bugs, just random issues. Ex. when debugging vs. deploying, I have to modify the underlying index.html file to 'fix' the relative path. Not a big deal, just another tiny cut.

Wpf is not that bad imo. But the fact no one at Microsoft is willing to touch it (i heard the originators were relocated) does not feel good at all.

WinUi, it's supposed successor, only has 5 people working on it, and seems like it's just waiting to be overtaken