3
If XAML has problems, why not just abandon it?
source link: https://www.mrlacey.com/2024/02/if-xaml-has-problems-why-not-just.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
If XAML has problems, why not just abandon it? ~ Matt Lacey
I often hear that XAML has problems, so you should use C# instead.
If you really strongly object to using XAML and can't be persuaded otherwise, feel free to only use C#. I'm not going to stop you. I'm more interested in you producing high-quality software that you can maintain and that provides value to people and they can easily use.
If you're not going to make a purely emotional decision, read on.
- If you already have existing XAML code, rewriting it probably isn't the best use of your time.
- XAML or C# is an artificial distinction. It was never the case that you were intended to only ever use XAML and not C# for the UI of anything but the most basic of applications. There are some things that are very hard in XAML, and there are some things that _should_ feel strange and unnatural when done in C#.
- There are better ways to write XAML than the very basic ways shown in almost all instructions and training material.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK