Hacker News Reader

Comment by _random_ | Hacker News Reader

Because XAML: 1) is a limited subset of WPF; 2) an intentionally chosen confusing name; 3) can't be used for desktop development (AFAIK) - and that is what a typical enterprise wants.

View on HN

Is this correct? It is my understanding that XAML is the client language that is used in WPF and Silverlight (which is a subset of WPF). Both WPF and Silverlight can be used for desktop or web development (although WPF leans to desktop and SL leans to web).

No, you are right. There are just small API differences in terms of available components.

XAML is the layout engine used in Silverlight, WPF and WinRT.

There are only differences in the amount of C# and C++ code in the XAML stack, and the set of available UI components.

XAML is not a layout engine, it's a language for instantiating objects. It does not even have to be used for GUI objects, just look at workflow foundation or BizTalk transforms.

XAML is not only a layout engine, yes I know.

We are discussing its place in GUI Frameworks.

No its simply not an engine, you are wrong. WPF or WPFe (Silverlight) or WinRT have layout engines, XAML can instantiate objects that call into the respective layout engines. Those same object can be created with normal code as well, no XAML at all.

First of all XAML is a language. Second of all Microsoft is now avoiding saying WinRT explicitly, for example: http://msdn.microsoft.com/en-US/library/windows/apps/hh87219.... Third of all "set of available UI components" kind of matters when you are building certain LOBs.

Reply on news.ycombinator.com