Reply to thread

Message

<blockquote data-quote="jawbroken" data-source="post: 87508" data-attributes="member: 14372">Yes, another thing to consider with WPF browser applications is that it is really a step backwards as far as compatibility goes; one of the nicest things about web applications was that you could pretty much use them from anywhere with a web browser, whereas with WPF you will begin locking people in to specific platforms again.This isn't necessarily a bad thing, but it is clear than Microsoft are trying to create a defacto standard for web applications that is incompatible with competitors platforms and thus lock people into their platform for another generation. It is clear that web applications are starting to scare them, so it is a smart move on their behalf.Again, this is just something to consider and not necessarily a dealbreaker, especially since it is probably the best way to deliver thick client functionality through a browser on the horizon. Then again, it is pretty much just a nicer way to automatically download and run applications from the web, as I understand it. As far as I can tell it is just a more tightly integrated version of Java WebStart or even C# ClickOnce. wikipedia says &quot;Although one gets the perception of the application running in the browser it actually runs in an out of process exe different from the browser&quot; for the WPF XAML browser applications, so I suspect I am right on this point.As MediaPortal is a Windows application perhaps this isn't a consideration, I am just a little wary about the possible impact on web applications in the future.</blockquote>

[QUOTE="jawbroken, post: 87508, member: 14372"] Yes, another thing to consider with WPF browser applications is that it is really a step backwards as far as compatibility goes; one of the nicest things about web applications was that you could pretty much use them from anywhere with a web browser, whereas with WPF you will begin locking people in to specific platforms again. This isn't necessarily a bad thing, but it is clear than Microsoft are trying to create a defacto standard for web applications that is incompatible with competitors platforms and thus lock people into their platform for another generation. It is clear that web applications are starting to scare them, so it is a smart move on their behalf. Again, this is just something to consider and not necessarily a dealbreaker, especially since it is probably the best way to deliver thick client functionality through a browser on the horizon. Then again, it is pretty much just a nicer way to automatically download and run applications from the web, as I understand it. As far as I can tell it is just a more tightly integrated version of Java WebStart or even C# ClickOnce. wikipedia says "Although one gets the perception of the application running in the browser it actually runs in an out of process exe different from the browser" for the WPF XAML browser applications, so I suspect I am right on this point. As MediaPortal is a Windows application perhaps this isn't a consideration, I am just a little wary about the possible impact on web applications in the future. [/QUOTE]

Verification