Hacker News Reader

Comment by pjmlp | Hacker News Reader

Why do developers keep mixing WPF, Silverlight and XAML?!

XAML is what counts in these stacks and it is still there.

XAML is a xml language for instantiating objects, whether it be a one of 3 similar but different GUI frameworks (WPF,Silverlight,WinRT) or say a workflow run-time (WWF).

Saying "XAML is what counts" is like saying "XIB is what counts" in the Apple world.

XAML is almost the same API, with differences in terms of where it is implemented (WPF, Silverlight, WinRT implementations have different sets of C#/C++ code), the available components and some classes.

However, it does share quite a lot across all frameworks where it is used.

Incorrect WPF, Silverlight, and WinRT are similar GUI frameworks much in the same way Cocoa is similar between iOS and MacOS. In Windows XAML can be used to instantiate objects from those frameworks, on the Apple side XIB's provide the same function.

I lack XIB experience. Can you also fully define GUI widgets just with XIB code like in XAML, where the whole graphic behaviour, transitions, events, skinning and themes is fully defined via XAML only?

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.

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