Discussion on: An alternative to Xaml for WPF

Hi,

The short answer is at the top of this article.
Long answer:

• I wanted to get a way to put more advanced behavior in the UI without the hurdle of Converters and Behaviors
• Keep MVVM pattern
• Play with fluent API because I love it :)
• Get rid of the xaml editor (which seems to improve with time)
• Be able to reuse any piece of code (I know that xaml allows reusability too)
• I'm also curious to see if there's any positive performance impact either during compilation time or runtime (but I didn't measure it yet)
• Some people knows C# well but not xaml, so it can be easier for them to develop UI using this library