Re: Major change proposal

It is good to run prothon under .net  but IMHO you will be better of 
continuing your current task of releasing prothon 1.0. Here are my reasons.
- You have already spent more than half a year coding prothon interpreter 
which works.
- Almost all of your 1.0 specification is done and you can release 1.0 by end 
of this year.
- If you built it, they will come and you know you can built 1.0 without a 
doubt.
- By having 1.0 under your belt, there will be lot more people who will create 
useful libraries and tool around it. 1.0 will also give you more credits to 
you work (like Jim Huggins for creating Jython in the past).
- By this time Jim Huggins, working with microsoft, will shed more lights on 
integrating dynamic language  on .net platform. You will know what will be 
major hurdles you need to cross, plus remember he is working for microsoft so 
he will get inside into .net which you can only dream of. You will have more 
time learn from his work (just like python and stackless).
- 1.0 will give you all implementation details you need to know to jumpstart  
on .net platform if you choose to do so (provided Jim is successful with his 
IronPython).
- And if you choose to do so, your work effort will be multiply by communitys' 
work on libraries and tools in parallel which you can take it with you 
under .net.
- Community will feel more involve since they have a programming language to 
work with. They might even start using prothon as soon as you have alpha 
release.

- Samir

On Tuesday 03 August 2004 12:35 am, Mark Hahn wrote:
> At OSCON last week, IronPython was announced. This is an implementation of
> Python running on the .net interpreter (CLI) from Microsoft.  The most
> surprising thing about the announcement was that it ran as fast as the
> normal Python interpreter.  Past attempts were dissapointing.
>
> Paul Prescod repeated some of this IronPython presentation at the Vancouver
> Python workshop that he held (Prothon was a big hit there by the way
> <grin>).  Paul brought to my attention something that caused me to lose a
> lot of sleep last night.
>
> If I were to put my current Prothon interpreter work aside for a while and
> switch to working on "IronProthon" (a Prothon to run on .Net), then I would
> have a fast reliable Prothon just as soon if not sooner, but more
> importantly, it would have the entire Microsoft .net library available to
> it.
>
> It would also have the Unix/Linux world available through the open source
> Mono project from Novell.  This open source version of .net project is at
> the 1.0 stage and was developed by the author of Gnome, so it is to be
> taken seriously.
>
> I looked seriously at using Parrot for an interpreter and almost everything
> wrong with Parrot is right with .net and mono.  It is stable and working.
> It has the library ready to use.
>
> The thing that caused me to lose a lot of sleep is that while this would be
> a great thing for the promotion and adoption of Prothon, it would mean
> shelving code that I have been working on 7 days a week for 7 months.
> Prothon comes first though.  Getting users of the language is more
> important than anything else.
>
> The nature of Prothon will change a bit.  It won't have the
> industrial-strength (scalable performance) advantage due to the unique
> engine.  IronPython will be identical in that regard.
>
> It will become Python3000.  In other words it will just become more of a
> direct competitior with Python (or to be more exact IronPython).  Our
> language features of Prototypes, Python fixes, enhancements, etc. will be
> our marketing points.
>
> I welcome feedback and thoughts on this major change.
>
>
> _______________________________________________
> Prothon-user mailing list
> [email protected]
> http://lists.prothon.org/mailman/listinfo/prothon-user