I agree that the big number of C# developers will favour SL adoption as the main RIA platform, but remember than that's only one of many languages supported by .NET and thus Silverlight, being VB de most used, but I don’t like it, so let's not talk about it. The DLR will be a huge bump for .NET adoption from other developers, specially from the Ruby and Python communities. For them, SL is a great opportunity to offer a richer experience than AJAX (we're still not there), coding in their own languages and easily sharing business logic, validations, data, etc. I remember a talk at TechED, I don’t remember the name of the guy, but he was talking about IronPython and told us (paraphrasing), you’re not the target of these (or the other DRL languages), if you’re happy coding on C#, MS will be happy, but our real target is the Python community.
So as a Python, Ruby or even JavaScript developer, what would you choose as a RIA platform having the DLR? Tooling and integration, and even the languages are not totally there yet, but I was recently looking at a project called Silverline <http://github.com/jschementi/silverline/tree/2642bc5b3709565a4037a8d38e7f97b185bbd505> , part of the IronRuby-Contrib project, that will help as a bridge for Rails Devs to SL. Sounds really compelling. Silverline also lets you run pieces of your Rails application on the client, removing the need to write a separate JavaScript or Flash application simply to move functionality to the client. This is accomplished by flagging certain actions as "client", and running the necessary pieces of your Rails appliation and Rails itself on IronRuby in the browser. Miguel A. Madero Reyes www.miguelmadero.com (blog) [EMAIL PROTECTED] (871)730-8319 (871)763-0020 Peten #509 Fracc Florida Blanca, 27260 Torreón, Coahuila "Please reconsider your environmental responsibility before printing this e-mail" The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jordan Knight Sent: Friday, 17 October 2008 11:09 AM To: listserver@ozSilverlight.com Subject: RE: [OzSilverlight] Success or Failure of SL.? >>> - numbers of developers (no point coming up with cool tools/technology if no one uses it) >>> - resources to help those developers (getting started / moving forward) As I said before, iI think c# developers are the easy sell... I think more focus needs to be placed on designers to get this puppy off the ground. BTW I am a developer by all means... I don't have a lot of design experience (well I think I do sometimes)... I need and want good developers who know their way around the required bits of SL/Expression to work with in the future. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barry Beattie Sent: Friday, 17 October 2008 11:00 AM To: listserver@ozsilverlight.com Subject: Re: [OzSilverlight] Success or Failure of SL.? On Fri, Oct 17, 2008 at 9:12 AM, Damian Edwards <[EMAIL PROTECTED]> wrote: > Actually there's probably less work because XAML is a controlled and strict > environment the tooling is much better and can be trusted more. Using the > designer and palettes in Expression Web or VS2008 to build your CSS styles > is not WYSIWYG and for experienced CSS coders is actually, usually, slower. > Compare that to Blend where creating reusable styles is a joy. so you're saying the development road-bumps are smoothed by the tooling for Silverlight? I wonder what you make of this then? http://www.sdtimes.com/MICROSOFT_CO_SPONSORS_ECLIPSE_PROJECT_FOR_SILVERLIGHT/About_OPENSOURCE_and_SILVERLIGHT_and_ECLIPSE_and_MICROSOFT_and_SOYATEC/32968 Look, at the end of the day, there's not going to be a lot of difference between Flex and Silverlight. an XML-type markup language to describe the UI, a Java-type language for logic and object creation. Meh. Same (basic) leopard, different spots. Tooling *is* important with quality intellesence, and designer-built interfaces. That's why in the Flex world the tool of choice (not exclusive) is built on Eclipse - to smooth the transition for those Java and ColdFusion developers working with Flex. Couple that with Adobe designer products pushing out Flex UI's. Microsoft has always had quality tooling with VisualStudio but where the "battle" will be fought (and it doesn't have to be red team Vs blue team but simply horses for courses) is ... (in order, my opinion) - the client runtime availability (the SL player Vs the Flash Player) and therefore the potential reach of the application (so what's wrong with SL being the perfect choice for inhouse apps with a fixed Windows-based SOE?) - numbers of developers (no point coming up with cool tools/technology if no one uses it) - resources to help those developers (getting started / moving forward) ------------------------------------------------------------------- OzSilverlight.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.8.0/1721 - Release Date: 16/10/2008 7:12 PM ------------------------------------------------------------------- OzSilverlight.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net ------------------------------------------------------------------- OzSilverlight.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net