Jasper and IronPython in an ASP.NET Application
Every single demo that I've seen of Jasper has involved people using ipy to dynamically interrogate the database, which is fine. Also, the ASP.NET demos of Jasper have used VB as the code-behind language.
Here's the problem: both of those scenarios that I will never use in production. I will not be using VB in production , nor will I be using ipy in production.
What I'd like to see is:
- an ASP.NET application with IronPython as the code-behind
- an ASP.NET application with Ruby as the code-behind
No problem. We should be able to post an ASP.NET demo app with IronPython 1.1 in the code behind. IronRuby isn't quite ready yet, but as soon as we can get a decent build and get Jasper integrated with the DLR (Dynamic Language Runtime) I will do a Ruby version of the same sample.
Just curious, but are you saying you would be willing to put an IronPython or Ruby app into production, but not the same app written in VB? I would be curious to hear the reasons why?
Thanks,
Andy
I'm not saying that VB isn't a production-quality language. I'm saying that in the circles of people I associate with, no one will use VB. I don't know a single programmer who would willingly choose to write their code in VB. I make no claims as to the prejudicial attitudes of said programmers- only that I no of no one personally who prefers VB as a development language.
That said, in that same group of people, many of them find Ruby to be hip and cool, and Python to be equally cool and powerful.
My next question of course is - why did Ruby get LINQ and IronPython didn't? Having a facility like LINQ in these super-small, iterative, flexible applications in the same vein as Ruby/Rails is immensely useful. Any thoughts on when LINQ will be available in IronPython?
Also, to clarify - you're saying that Jasper is purely a .NET library that is exposed in such a way that IronPython (which does NOT require Orcas, it runs on .NET 2.0) can utilize it. IronPython for Jasper is actually not part of the DLR, correct?
Thanks for the information. I would suggest that folks give VB a chance occansionally.IMHO, particularly with the new features coming on line in VB9 (lambda expressions, Linq) and beyond (true dynamism) I think VB is becoming a very compelling dynamic language.And based on constantly switching between languages while working on Jasper, between Python, Ruby, and VB – I can’t say I can pick one over the others.
That said, the DLR will initially support four different .NET languages (IronRuby, IronPython, VBX, and managed Javascript) and we are designing the Jasper framework to work in all, so the developer will be free to pick their dynamic language of choice.
A couple of clarifications – Linq is supported by IronPython 2.0 but not IronPython 1.1.Since the initial CTP of Project Jasper is not integrated with the DLR, we only support VB 9 and Iron Python 1.1 – and only the former supports Linq.
Also, Project Jasper CTP is built on top of .NET framework 3.5 Beta 1 (Orcas release).We could have built it over .NET framework 2.0, but we wanted Linq support.As I said before, as on the next CTP release Jasper will be built over the DLR which is targeted as a post Orcas release.
Andy
Andy,
Let me know when there are samples available showing a Jasper/ASP.NET app driven by IronRuby please 
thanks,
Kevin
While I'm getting more and more facile with C#, I still prefer to code production apps in VB and I can vouch that Kevin does not know me personally.
Sorry, but I just could NOT resist!
Still no IronRuby Jasper demos available? Until I see IronRuby demos available for Jasper, I'm going to have to pass.. I just simply cannot bring myself to work in VB, even if it is the fantastically dynamic, magically delicious new VB9.
Same for me. I've writing production data-centric projects in VB since the Professional Extensions for Version 1.0 (a.k.a. Rawhide) and in VBA since Access 1.0. There are many thousands (maybe millions) of production projects written in the many versions of VB; I would guess at least two orders of magnitude more than C#.
--rj
http://oakleafblog.blogspot.com
I don't deny the sheer volume of available VB code. All I'm saying is that I've seen VB before, and I know what it looks like and how it works. What I want to see is whether or not its feasible to write an IronRuby Jasper application.
I can't possibly be the only person alive who wants to make a direct comparison of IronRuby on Jasper to Ruby on Rails...
