<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Silverlight, Flash as seen by Microsoft</title>
	<atom:link href="http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/</link>
	<description></description>
	<lastBuildDate>Thu, 10 Sep 2009 20:01:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jp</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-17</link>
		<dc:creator>jp</dc:creator>
		<pubDate>Wed, 24 Oct 2007 11:32:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-17</guid>
		<description>Coming from a java and .net background and making the move to Flex some months ago, I must say I miss the relative ease of development and maturity of tools found in the microsoft environment. The flex community and resources are almost nonexistant in comparison.  Finding help, good examples, resources, etc is like pulling teeth in Flex. If you have a common problem, sure you can find 20 people with the same issue, but no one with a common solution.  If microsoft makes it easier for developers, I think they will gain a credible advantage and very quickly.

That said, the main draw back to silverlight is the lack of firefox support.  With firefox now having a 10% market share, I don´t believe a lot of public web sites will alientate 10% of their market.   Silverlight will work for inhouse applications however.

The other advantage I see to flex, is the opensource nature. This should mature the product very rapidly (see gripe number one) and keep it developing quickly.  Plus the integration with Media Server and the growing number of open source alternatives helps. Silverlight will have some sort of server backing it, but until pricing is released, who knows.</description>
		<content:encoded><![CDATA[<p>Coming from a java and .net background and making the move to Flex some months ago, I must say I miss the relative ease of development and maturity of tools found in the microsoft environment. The flex community and resources are almost nonexistant in comparison.  Finding help, good examples, resources, etc is like pulling teeth in Flex. If you have a common problem, sure you can find 20 people with the same issue, but no one with a common solution.  If microsoft makes it easier for developers, I think they will gain a credible advantage and very quickly.</p>
<p>That said, the main draw back to silverlight is the lack of firefox support.  With firefox now having a 10% market share, I don´t believe a lot of public web sites will alientate 10% of their market.   Silverlight will work for inhouse applications however.</p>
<p>The other advantage I see to flex, is the opensource nature. This should mature the product very rapidly (see gripe number one) and keep it developing quickly.  Plus the integration with Media Server and the growing number of open source alternatives helps. Silverlight will have some sort of server backing it, but until pricing is released, who knows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Khaled</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-16</link>
		<dc:creator>Khaled</dc:creator>
		<pubDate>Sat, 20 Oct 2007 18:14:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-16</guid>
		<description>Well, Adobe Flash still have a problem with support for Bi-directional Languages like Arabic and Hebrew, Right-to-Left. And this is something solved by Micro$oft long time ago. Adobe seems not to be much interested in fixing this in Flash or they might have a problem in implementing it properly.

Wouldn&#039;t be possible to create a component(or anything similar) to be added to Visual Studio .Net so developers can be able to use any of the .Net languages to develop applications for Flash? -- this is just an idea that crossed my mind and not sure of its merit.</description>
		<content:encoded><![CDATA[<p>Well, Adobe Flash still have a problem with support for Bi-directional Languages like Arabic and Hebrew, Right-to-Left. And this is something solved by Micro$oft long time ago. Adobe seems not to be much interested in fixing this in Flash or they might have a problem in implementing it properly.</p>
<p>Wouldn&#8217;t be possible to create a component(or anything similar) to be added to Visual Studio .Net so developers can be able to use any of the .Net languages to develop applications for Flash? &#8212; this is just an idea that crossed my mind and not sure of its merit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thierry</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-15</link>
		<dc:creator>Thierry</dc:creator>
		<pubDate>Wed, 17 Oct 2007 15:37:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-15</guid>
		<description>@James:
Those are very good points. Thanks for presenting them. They seems obvious to me now, but not before you talked about them.
Thanks!

@wekempf:
I&#039;d will just temper a bit the affirmation you extracted from my post: I don&#039;t think that flash have more &lt;strong&gt;developers &lt;/strong&gt;than .NET, but flash have a bigger community of &lt;strong&gt;designers&lt;/strong&gt;.

Designers are not developers, and developers are often poor designers. Sure, there are good designers that are good developers, but those are like pearls; extremely rare.

.NET is more geared towards a team, with designers and programmers working together to deliver a final product, and I&#039;m not sure that they will outnumber the quantity of flash designer, simply because I think silverlight might attract more medium to big entity, and not that much LLC or &quot;mom based&quot; business.
Those will stay in the field of Flash, in my opinion, at least for the years to come.

Now, neither silverlight nor javaFx (which will be my next post, I&#039;m working on it) are mature products yet.
Both are just draft for the moments, with heavy development being made on the core of those projects in that precise moment, so I don&#039;t think that anybody can predict anything now.
In that view, I don&#039;t think that the ability to run python or ruby code can attract that much peoples and make them throw away years of flash to implement everything in another language, as appealing that this language might be.

But true, Adobe might have to watch closely, and to listen real good about what is important for the peoples that might use their products.
In the end, ease of development, reachability, user base and support will be everything that will motivate the choice.
Both Adobe and Ms are big, strong enterprises that won&#039;t disappear in a couple of months, and it&#039;s not on the reputation of the two that the choice will be made.
At least not if someone with a bit of intelligence have to make that choice.</description>
		<content:encoded><![CDATA[<p>@James:<br />
Those are very good points. Thanks for presenting them. They seems obvious to me now, but not before you talked about them.<br />
Thanks!</p>
<p>@wekempf:<br />
I&#8217;d will just temper a bit the affirmation you extracted from my post: I don&#8217;t think that flash have more <strong>developers </strong>than .NET, but flash have a bigger community of <strong>designers</strong>.</p>
<p>Designers are not developers, and developers are often poor designers. Sure, there are good designers that are good developers, but those are like pearls; extremely rare.</p>
<p>.NET is more geared towards a team, with designers and programmers working together to deliver a final product, and I&#8217;m not sure that they will outnumber the quantity of flash designer, simply because I think silverlight might attract more medium to big entity, and not that much LLC or &#8220;mom based&#8221; business.<br />
Those will stay in the field of Flash, in my opinion, at least for the years to come.</p>
<p>Now, neither silverlight nor javaFx (which will be my next post, I&#8217;m working on it) are mature products yet.<br />
Both are just draft for the moments, with heavy development being made on the core of those projects in that precise moment, so I don&#8217;t think that anybody can predict anything now.<br />
In that view, I don&#8217;t think that the ability to run python or ruby code can attract that much peoples and make them throw away years of flash to implement everything in another language, as appealing that this language might be.</p>
<p>But true, Adobe might have to watch closely, and to listen real good about what is important for the peoples that might use their products.<br />
In the end, ease of development, reachability, user base and support will be everything that will motivate the choice.<br />
Both Adobe and Ms are big, strong enterprises that won&#8217;t disappear in a couple of months, and it&#8217;s not on the reputation of the two that the choice will be made.<br />
At least not if someone with a bit of intelligence have to make that choice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wekempf</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-14</link>
		<dc:creator>wekempf</dc:creator>
		<pubDate>Wed, 17 Oct 2007 10:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-14</guid>
		<description>You several times made reference to &quot;Flash winning due to the number and quality of developers&quot; (paraphrased, not an exact quote).  Thing is, the number of .NET developers far out weighs the number of Flash developers (and I won&#039;t get into a discussion of the quality of the developers in either camp... both have good and bad developers).  Further, the multilanguage support of Silverlight gives an advantage to Silverlight as well, because the numerous Python and Ruby developers have some knowledge to bring to the table as well.  So, if you&#039;re going to evaluate things solely on the programmer base, I&#039;d say Flash has very little chance.  Of course, that&#039;s over simplifying things, but I did so to make my point.  In reality, Silverlight does have a hill to climb, but at this point in time it&#039;s Adobe that has to make moves in order to keep it&#039;s dominance in the market.</description>
		<content:encoded><![CDATA[<p>You several times made reference to &#8220;Flash winning due to the number and quality of developers&#8221; (paraphrased, not an exact quote).  Thing is, the number of .NET developers far out weighs the number of Flash developers (and I won&#8217;t get into a discussion of the quality of the developers in either camp&#8230; both have good and bad developers).  Further, the multilanguage support of Silverlight gives an advantage to Silverlight as well, because the numerous Python and Ruby developers have some knowledge to bring to the table as well.  So, if you&#8217;re going to evaluate things solely on the programmer base, I&#8217;d say Flash has very little chance.  Of course, that&#8217;s over simplifying things, but I did so to make my point.  In reality, Silverlight does have a hill to climb, but at this point in time it&#8217;s Adobe that has to make moves in order to keep it&#8217;s dominance in the market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James H</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-13</link>
		<dc:creator>James H</dc:creator>
		<pubDate>Wed, 17 Oct 2007 09:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-13</guid>
		<description>This is a good summary of the situation. Here are some additions and clarifications:

Languages supported:
1. Silverlight already has the multilanguage support of .NET platform.
2. Java(the platform) has many languages implemented but the Java language is the most supported. JavaFX Script is a new scripting language for the platform. (JavaFX Mobile aims to unify APIs for mobile phones and is somewhat tangential to comparisons with Silverlight/Flash, so I won&#039;t mention it more)
3. Flash&#039;s VM is titled &quot;Actionscript VM&quot; (AVM) and only Actionscript(which is really two languages, AS1/2, and AS3) is officially supported with AVM. An alternative open-source language compiling to AVM, haXe, is available. Finally, a tech demo at the recent Adobe MAX conference showed C++ code compiled to run on AVM. We don&#039;t know yet if anything will come of the demo, but it opens many, many possibilities.

Application packaging:
1. I&#039;m not sure exactly what Silverlight offers. I&#039;m sure there&#039;s a browser plugin, and a way to build executable binaries, since the former is a major feature and .NET already does the latter.
2. Java currently offers applets in the browser and Java Web Start outside of it. Java Web Start acts as its own installer/package manager tool. Executable binaries can also be built. JavaFX does nothing new for packaging AFAIK.
3. Flash is a ubiquitous browser plugin, can build executable &quot;projector&quot; files(to a limited number of target platforms), and now has a Java Web Start-like package manager with the AIR system. AIR assists in access to lower-level details of the OS and platform that Flash normally restricts.

UI design:
1. Silverlight supports Microsoft&#039;s touted XAML markup format for interface design.
2. JavaFX Script has the primary goal of UI markup in mind. 3. Flash has two modes of interface design: graphically with the Flash IDE, and using MXML markup with Adobe&#039;s Flex toolkit. Flex aims to be more developer/app-oriented than Flash. Note that both MXML and XAML are XML-based. Don&#039;t know how similar they are, though...</description>
		<content:encoded><![CDATA[<p>This is a good summary of the situation. Here are some additions and clarifications:</p>
<p>Languages supported:<br />
1. Silverlight already has the multilanguage support of .NET platform.<br />
2. Java(the platform) has many languages implemented but the Java language is the most supported. JavaFX Script is a new scripting language for the platform. (JavaFX Mobile aims to unify APIs for mobile phones and is somewhat tangential to comparisons with Silverlight/Flash, so I won&#8217;t mention it more)<br />
3. Flash&#8217;s VM is titled &#8220;Actionscript VM&#8221; (AVM) and only Actionscript(which is really two languages, AS1/2, and AS3) is officially supported with AVM. An alternative open-source language compiling to AVM, haXe, is available. Finally, a tech demo at the recent Adobe MAX conference showed C++ code compiled to run on AVM. We don&#8217;t know yet if anything will come of the demo, but it opens many, many possibilities.</p>
<p>Application packaging:<br />
1. I&#8217;m not sure exactly what Silverlight offers. I&#8217;m sure there&#8217;s a browser plugin, and a way to build executable binaries, since the former is a major feature and .NET already does the latter.<br />
2. Java currently offers applets in the browser and Java Web Start outside of it. Java Web Start acts as its own installer/package manager tool. Executable binaries can also be built. JavaFX does nothing new for packaging AFAIK.<br />
3. Flash is a ubiquitous browser plugin, can build executable &#8220;projector&#8221; files(to a limited number of target platforms), and now has a Java Web Start-like package manager with the AIR system. AIR assists in access to lower-level details of the OS and platform that Flash normally restricts.</p>
<p>UI design:<br />
1. Silverlight supports Microsoft&#8217;s touted XAML markup format for interface design.<br />
2. JavaFX Script has the primary goal of UI markup in mind. 3. Flash has two modes of interface design: graphically with the Flash IDE, and using MXML markup with Adobe&#8217;s Flex toolkit. Flex aims to be more developer/app-oriented than Flash. Note that both MXML and XAML are XML-based. Don&#8217;t know how similar they are, though&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Holley</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-12</link>
		<dc:creator>Will Holley</dc:creator>
		<pubDate>Wed, 17 Oct 2007 08:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-12</guid>
		<description>Hi Ryan,

My impression is that the future of Silverlight (1.1) is geared more towards building rich client applications of the kind that have been difficult to build in Flash (although this  is also changing with Flex2, Air etc). As I see it there are 2 major wins for Silverlight over flash in this area:

1. the support for .NET framework languages as well as JavaScript, (Iron)Python, (Iron)Ruby means that there is a large amount of code out there that you can port into you apps.

2. You have all the tooling for .NET at your disposal - visual studio, expression tools, all the testing tools / frameworks, ability to use continuous integration etc that as far as I&#039;m aware are generally lacking in the flash world.

That said, Silverlight 1.1 is still in alpha and theres a lot missing and unknown about how the process of developing rich client apps in it will work.</description>
		<content:encoded><![CDATA[<p>Hi Ryan,</p>
<p>My impression is that the future of Silverlight (1.1) is geared more towards building rich client applications of the kind that have been difficult to build in Flash (although this  is also changing with Flex2, Air etc). As I see it there are 2 major wins for Silverlight over flash in this area:</p>
<p>1. the support for .NET framework languages as well as JavaScript, (Iron)Python, (Iron)Ruby means that there is a large amount of code out there that you can port into you apps.</p>
<p>2. You have all the tooling for .NET at your disposal &#8211; visual studio, expression tools, all the testing tools / frameworks, ability to use continuous integration etc that as far as I&#8217;m aware are generally lacking in the flash world.</p>
<p>That said, Silverlight 1.1 is still in alpha and theres a lot missing and unknown about how the process of developing rich client apps in it will work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thierry</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-11</link>
		<dc:creator>Thierry</dc:creator>
		<pubDate>Sun, 14 Oct 2007 11:04:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-11</guid>
		<description>Thanks Ryan.
I have to admit I&#039;m pretty impressed to have caught your attention. And a bit proud that you call it a &quot;really good writeup&quot;.
As I said in my post, I&#039;ll keep looking about this silverlight/javaFx gig, and I&#039;ll continue to comment my views on it.

And if I had any questions about Flash that I could not find an answer, you will hear of me.

And by the way, sorry for all those spellings errors.
I was really horrified when I proof readed this post this morning.
Note to self, don&#039;t publish a post at 3am, it&#039;s a __BAD__ idea...</description>
		<content:encoded><![CDATA[<p>Thanks Ryan.<br />
I have to admit I&#8217;m pretty impressed to have caught your attention. And a bit proud that you call it a &#8220;really good writeup&#8221;.<br />
As I said in my post, I&#8217;ll keep looking about this silverlight/javaFx gig, and I&#8217;ll continue to comment my views on it.</p>
<p>And if I had any questions about Flash that I could not find an answer, you will hear of me.</p>
<p>And by the way, sorry for all those spellings errors.<br />
I was really horrified when I proof readed this post this morning.<br />
Note to self, don&#8217;t publish a post at 3am, it&#8217;s a __BAD__ idea&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Stewart</title>
		<link>http://www.webalis.com/2007/10/silverlight-flash-as-seen-by-microsoft/comment-page-1/#comment-10</link>
		<dc:creator>Ryan Stewart</dc:creator>
		<pubDate>Sat, 13 Oct 2007 23:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.webalis.com/2007/10/13/silverlight-flash-as-seen-by-microsoft/#comment-10</guid>
		<description>Really good writeup. I&#039;m not sure we have an &quot;answer&quot; to Silverlight but we&#039;ve been putting some new stuff in the Flash Player like support for H.264 video. If you have any questions, let me know.

=Ryan
rstewart@adobe.com</description>
		<content:encoded><![CDATA[<p>Really good writeup. I&#8217;m not sure we have an &#8220;answer&#8221; to Silverlight but we&#8217;ve been putting some new stuff in the Flash Player like support for H.264 video. If you have any questions, let me know.</p>
<p>=Ryan<br />
<a href="mailto:rstewart@adobe.com">rstewart@adobe.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.294 seconds -->
