Blog to discuss Midnight Coders products, features, ideas and trends in development of Rich Internet Applications

Tuesday, May 01, 2007

Thoughts on Silverlight, Adobe, Flex and us

Microsoft has taken the covers off of Silverlight. The industry seems to be stunned as the execution and the technology facts are quite impressive. I will not go into the analysis of the Silverlight features, there are plenty of other resources for that. Instead, I would like to discuss what the news has in it for Flash/Flex, Adobe and us(Midnight Coders).

Flash/Flex. Silverlight is clearly a competitor to Flash/Flex. Competition typically results in two things: (1) Consumers benefit from lower pricing (2) Competing technologies tend to improve to deliver better, faster, cooler features. For example, availability of Silverlight Streaming may certainly have a profound impact on the pricing of products like FMS (and our own WebORB Enterprise). Another example is the plugin processing speed. Scott Guthrie in his interview with Channel 9 mentions the speed of the Silverlight virtual machine (CLR/DLR) and indirectly refers to an alternative product saying Silverlight is about 20 times faster. I am not sure if he's talking about Flash9, though something tells me that's what MS would benchmark their product against.

Adobe. Things will never be the same for Adobe. With a single move, Microsoft put .NET on the RIA map, the same .NET Adobe has been completely ignoring with Flex. This means that in theory every single .NET developer is qualified to be an RIA developer, but unfortunately they will remain in the Microsoft's camp. Should Adobe try to gain any traction with the .NET folks? Absolutely! Giving up on them would be letting MS eat Adobe's lunch without a fight. The key is to focus on the material and immaterial assets Adobe has. I believe there are three:
  1. Adobe still has the majority of the graphics/art designers in its camp. The role of the designers in the RIA space is extremely important. That's a huge asset.
  2. Flash plugin market penetration. Many people say it is very hard to get the deployment numbers Flash player has and MS may fight an uphill battle to get the same ubiquity with Silverlight as Adobe has with Flash. I tend to disagree with this argument. Microsoft can get the same number overnight just by doing a "security update" and install Silverlight onto every single Windows XP, 2000, 2003 and Vista box.
  3. Platform/OS agnostic approach. Unlike MS, Adobe has no vested interest to stick to a particular operating system or a suite of server-side products (databases for example). As a result, Adobe's product vision *must* be "Flex is for everyone, Flex is for all". No matter if you are .NET, Java, PHP, Ruby, Python (or even Prolog) developer, you should be able to get the same quality of service and support when building an RIA with the backend of your choice.
What should Adobe do now in response to Silverlight? Here's my top ten:
  1. Embrace ALL popular languages as equal citizens of the Flex ecosystem
  2. Provide comprehensive backend implementation for all supported languages. That would include remoting, data management, messaging, and tooling.
  3. Simplify application Flex development live cycle. Rely on code generators and development workflow automation. Look at what we did with WDMF, this is the kind of things developers LOVE.
  4. Open up, document and standardize on-the-wire protocols
  5. Bundle FMS and FDS together
  6. Create a competing online streaming hosting service with even more hard drive space and bigger bandwdth pipes than MS.
  7. Pay attention and nourish small to medium size businesses. Let them use the product even if it means no revenue.
  8. Consider Visual Studio plugins/compiler for Flex development. I hear many .NET developers complain about their experiences with Flex Builder. I tend to agree, with all things being equal, Visual Studio is lighter and faster.
  9. This is a wild one (and kind of contradicts #8), but the benefits are huge: Introduce support for .NET languages in Flex Builder. Why lock people in to ActionScript? No reason one would not be able to program Flex in C#..
  10. Finally partner with Midnight Coders :)
Midnight Coders/WebORB. Our product is designed to be completely agnostic to the client technology. Today we support Flex, Flash and AJAX clients and can connect them to a variety of the backend systems (.NET, PHP, Ruby on Rails and Java (no Flex support for Java though)). As a result, it would make perfect sense to add Silverlight to the list of supported clients. That would open up a lot of interesting opportunities. For example, tighter integration between Silverlight clients and PHP or Ruby backends; server-to-client method invocation, perhaps even support for WDM(S?) :) We are not rushing there yet, our primary focus is still Flex. Even though it sure would be nice to do all development in Visual Studio, I believe Flex is superior to Silverlight
especially when it is integrated with .NET through WebORB.

Technorati tags: , , ,

7 Comments:

Blogger barry.b said...

I wonder how much of this (silverlight) adobe saw coming and to what degree?

and, because of that, I wonder how much of what adobe's actions from now on will be pro-active vs re-active?

how about MidnightCoders? did you guys see silverlight coming and if so, when it was going to go down?

6:41 AM

 
Anonymous Matthew Fabb said...

Microsoft has included IE7 in a security update, yet looking at various browser statistics and the majority of IE users still use IE6, despite that IE7 has been out since last year. So I would say that even if MS did include Silverlight as an automatic update, they will still have an uphill battle to get the penetration numbers that the Flash player has.

However, while I think Silverlight has a long way to go to become a serious competitor to Adobe's Flash/Flex I do think the competition is good and likely result in better development products all around.

9:36 AM

 
Anonymous Mike said...

Good Point Mark...

Adobe to purchase TMC :-)

Best of Luck

7:43 AM

 
Anonymous Kim said...

Thank you for bringing such nice posts. Your blog is always fascinating to read.

8:52 AM

 
Anonymous Jassi said...

Nice Article, As you stated Silverlight is realativley new to compare with Flex, and will take some time (To become a serious competitor).

This can be very much shorten by the .net developers who will using silverlight in near future(coz community is HUGE). Also, i am preety sure MS must have done their part reasearch to overlap flex functionality over .net and try to make it "easier" in their product.

2:30 PM

 
Anonymous Anonymous said...

I am more than happy that at last I found someone sane at the Adobe camp. I am a C# developer. But always I inclined towards Flash. Very long time ago I have predicted this situation and in forums and comments like this, I have told that Adobe is making the same mistake that Sun did with Java. But all of reaction was like this: "ActionScript is a very high level modern programming language" or "Flex does not need to provide a better support for .NET. After all who is using .NET?" and so on...
I like Flash because is it more mature and more beautiful. But with Silverlight 2 on the way - with C# programming even on client side - why should I use Flex?
And why companies with good products always behave bad - Adobe, Sun or even Apple that ignores all reported bugs for safari - and Microsoft with IE and Windows always behave good enough (You have free ide for developing on .NET: Visual Studio Express Edition! Nothing with same quality exists for Flex).
Cheers!

7:53 PM

 
Blogger Beau said...

As a developer in many programming and scripting languages, in my opinion I think ActionScript is among some one of the worst.

The syntax is a bit unorthidoxed. The learning curve was similar to swimming against the current.

The cost involved with Flash is expensive in a small/medium business model. Software costs, training, FMS, etc.

I'm not trying to bash Flash, but it's about time it got some competition. Definitely a smart move by Microsoft, they can really make an impact in this market. With XAML and .NET backing it up, I see no reason for failure.

8:59 PM

 

Post a Comment

<< Home