Well, looks like I'm going to be eating pie. I didn't get my translator done and, while Leo did some damned impressive work, he didn't get finished either (in large part, I suspect, because I didn't get the translator finished back at the beginning of June as I'd originally planned) so I need to scare up an oven for a while. I figure if I'm going to get pasted with a pie, it's going to be a good pie, and I don't like the no-bake Key Lime pies as much as the baked one.
I'm going to work up a post-mortem of the project, so we can work out what went wrong, what went right, and what needs addressing. That should be fun, but if you don't ask "Where the heck did you screw up" for projects that didn't succeed (hell, for projects that did succeed, even) then you'll just make the same damn mistakes again and again. That's dull--I'd much rather make new mistakes, thanks. :)
FWIW, this project is not going to die. We're too close to actually being finished, and it'd be too damned useful to have it working, to let it die now. Who knows, maybe we can manage to get things going for a run at YAPC::EU this year. That'd be cool.
Posted by Dan at July 24, 2004 05:21 PM | TrackBack (3)Thanks a lot for the effort, and thanks for not giving up on the project - even if the time and hardware got in the way! You guys have done an impressive piece of work in virtually no time.
I hope you and Leo will continue with the same attitude after OSCON - what mathers most is that Parrot outruns Python (and other HLLs), not when.
I do think it's a bad publicity for Parrot. And I think bad publicity is better than none.
Posted by: David Garamond at July 27, 2004 02:53 PMWell, it's a little unfortunate, but not entirely unexpected to be on the receiving end of the pie.
*I'm* not giving up on Parrot. And when I'm done with my thesis, I'll mention the stuff I've learned from looking at SBCL's internals and see whether there are other lurkers seriously thinking about Common Lisp on Parrot.
Keep up the good work, I believe Parrot can be the way to solving the "choosing the language on the basis of the library support for your project" problem, and this seems like a fine opportunity to make sure that Lisp gets in on the renaissance, too.
Dan, can you provide a brief statement about how fast Parrot is vs. native Python on the parts you do have implemented?
Posted by: Armand at July 30, 2004 12:41 PM