Re: PHP on .NET DLR

 The point here is not about promoting or not promoting Silverlight. The point here is your commitment to the php developers, and whether you will do your best to ensure that they can maximize their productivity.

On Fri, Aug 10, 2007 at 03:08:42PM -0700, Andi Gutmans wrote:
> Btw, Silverlight is not an open-standard and not cross-platform. While I
> see advantages of having the PHP syntax work on Silverlight (and it'd be
> nice if someone does it), I think the open-source community should not
> support Silverlight.

 What we need is PHP on .NET. Silverlight is merely one of the reasons. The egregious activity you are talking about--promoting silverlight--is being carried out by Mono, who have already ported it to Linux. PHP on the platform will have little impact on the platform itself, but on the other hand will help the existing PHP devs to use their skillset on yet another field.  If you want to resist SL owing to its lack of adherence to open standards, then you should get Novell to stop porting it to Linux. PHP on .NET is a completely different topic. It just gives existing PHP developers an additional and OPTIONAL interface to play around with. It won't really help the adoption of the platform, which is a client side technology.



> It's bad for the industry. We are better off supporting Ajax and the
> OpenAjax alliance (http://www.openajax.org/) then a proprietary
> technology. The last thing we need in this industry is to have one
> vendor gain control of the Web. Ajax today is far from perfect but the
> solution is to make enhancements as open-standards and not in a
> proprietary way.

 Again, php on dotnet is not involved in any of the above nefarious activities. MS already has python and ruby on .NET, so as such, one more language is not going to dramatically change anything.  Your argument also makes it appear that python and ruby are less opensource because they enthusiastically welcomed their addition to the DLR.


> 
> That said, from a PHP point-of-view our stance has always been to
> interoperate with as many popular technologies as possible, whether
> open-source, open-standard or proprietary. So I think in this context
> it'd be good to consider supporting things like Silverlight or MS Ajax
> (http://www.codeplex.com/phpmsajax) but not as the technology we want to
> encourage to "win".

 OK, we already have PHPAjax and everything. So when are we going to show the same courtesy to .NET?


 Thanks.