top | item 44778401 (no title) Kerbiter | 7 months ago I disagree, WPF is quite good to use, and WinForms approach to keeping UI as code is quite moronic. I would say WPF is where it should've stopped. discuss order hn newest HumblyTossed|7 months ago WPF sucks. I rather like expressing the UI in code. Having to deal with so much XML (XaML) is annoying as fuck. solid_fuel|7 months ago The workflow on WPF was so much more painful than winforms, which had a decent WYSIWYG designer and solid integration with visual studio.WPF in comparison was slow, memory hungry, and difficult to learn.I tried 5 times to make a WPF application but it didn’t even have all the same basic controls that WinForms supported. load replies (1)
HumblyTossed|7 months ago WPF sucks. I rather like expressing the UI in code. Having to deal with so much XML (XaML) is annoying as fuck. solid_fuel|7 months ago The workflow on WPF was so much more painful than winforms, which had a decent WYSIWYG designer and solid integration with visual studio.WPF in comparison was slow, memory hungry, and difficult to learn.I tried 5 times to make a WPF application but it didn’t even have all the same basic controls that WinForms supported. load replies (1)
solid_fuel|7 months ago The workflow on WPF was so much more painful than winforms, which had a decent WYSIWYG designer and solid integration with visual studio.WPF in comparison was slow, memory hungry, and difficult to learn.I tried 5 times to make a WPF application but it didn’t even have all the same basic controls that WinForms supported. load replies (1)
HumblyTossed|7 months ago
solid_fuel|7 months ago
WPF in comparison was slow, memory hungry, and difficult to learn.
I tried 5 times to make a WPF application but it didn’t even have all the same basic controls that WinForms supported.