Laura Creighton wrote: > In a message of Mon, 12 Nov 2007 19:53:33 +0100, Martijn Faassen writes: [snip] >>> Tim is very Ruby focused. He's not interested in python, he said, >>> because 'the ruby community is more vibrant'. Vibrant is measured >>> in body-count. >> body-count? As in how many people are part of it (I imagine Python would >> do pretty well compared to Python) or how many people die in horrible >> flame wars? :) > > I think 'how many people attend Ruby developers conferences' and > 'how many people use rails' but I am not 100% convinced of that.
I'm convinced the body count of Python users is probably still quite a bit larger than Ruby users. I also have a strong suspicion far more people are using Python web frameworks than there are people using Rails, hype aside, but I may be wrong about that. [snip John Rose] > And we left with him very impressed. Wew had a blast. I think he > would liek to attend a Sprint. And he would like it if we made > our next pypy focus -- getting the jit to work with the JVM. > > Wouldn't that be fun. Yes, that'd be of great practical importance, too. :) I have this vague dream of making Zope 3 (and Grok) run on the JVM using PyPy. Being able to use the Java libraries would be nice. >>> There is nothing but good news here. Be happy for us. >> All right, I'm happy for you. :) > > Thank you, and we will keep your concerns under consideration. > But please remember that the PyPy dev team needs to eat, pay > rent, and the like. While developing a Ruby front end may > not be the most fun thing we could do, it may be plenty more > fun than the other things we would end up doing instead just > to make the financial ends meet. As someone who needs to eat and pay rent and the like I think I know what you're talking about. I think making it practical and useful to run a PyPy-based Python interpreter in production projects is probably the best shot this project has at becoming more self-sustaining. You're close. So I'll definitely complain if you spend a lot of time on Ruby (or Smalltalk for that matter) before Python's all the way there. I think that'd be a bad idea for a whole range of reasons - get the last 10% done for Python first before you take even more on your plates. We all know that last 10% tends to be the hardest part. Focus is important. If you can't make that work for Python, you'd have a hard time making it work for any other language too (or convincing people that you can). Of course I realize I have no real voice in this project, but that's my input. Regards, Martijn _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
