Slashdot Mirror
Parrot: For Real
Thanks to Pudge of Slashteam for pointing out that very early version of Parrot has been released. You may recall Parrot from The April Fool's joke - but it's coming to life.
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
I can almost feel someone contemplating a sever side module for apache using this as an embedded web page script.
Yikes. I think I just described C#.
John
John
Looks like the roster is coming home to rest. I still think it is going to take a long time to get either side to convert or give and inch, but at least someone is pushing forward.
It will be interesting to see the beta scripts that get pumped out of this.
Neck_of_the_Woods
#/usr/local/surf/glassy/overhead
I am still not convinced that this Parrot would voom if you put 5000 volts through it.
The only reason it was standing before was because it had been nailed to the stick.
I emediatly thought of Monty Pythons parrot scetch.
Cracks me up just thinking about it. Its nice to think of something else for a while
There isn't much like the scent of a fresh harddisk
Thank you, Captain Obvious.
Wait a minute. I thought that Parrot (the package, not the April Fool's Joke) was supposed to be the common VM for Perl and Python, or at least that's what I gathered from the mailing list postings I read about it some time back.
The joke was about merging the syntax from the languages, but the real Parrot is about the VM. I think. :-) The details are really sketchy, and I don't have time to look at the code today (esp. since I'm on Solaris and I doubt it'd even compile).
Actually no.
The guy who orchestrated the April Fool's Joke is the pumpking for it. The idea of them working together was a pipe dream that influenced the joke.
Why the hell would anyone want to clone Ruby?
Unlike the joke, it is not a combined language !!! It started as an idea as a 'shared bytecode/runtime environment that could be used by both Perl 6 and a future version of Python'
Right now it is a interpreter that does assembly to bytecode only for now as far as I can tell...
Was this only inspired by the April fools joke, or was the 'joke' just a clever way of telling people something like that was in development but to confuse us, then surprise us?
In other words, is larry wall and the python guy collaborating efforts to bring us a new language derived from both? or is this some hackers bringing an actual product out of the joke.
Art imitating life, or life imitating art?
Guido:I wasn't expecting Parrot...
Larry: Nobody expects Parrot! Our chief trait is laziness...laziness and impatience...impatience and laziness...Our two traits are laziness and impatience...and hubris...Our *three* main traits are laziness, impatience, and hubris...and a ridiculous habit of quoting JR Tolkien...Our *four*..no... *Amongst* our traits...are such elements as laziness, impatience...I'll come in again.
http://slashdot.org/article.pl?sid=01/03/28/174223 7&mode=thread
shit, this was meant to be a reply to this
Wait a minute. I thought that Parrot (the package, not the April Fool's Joke) was supposed to be the common VM for Perl and Python, or at least that's what I gathered from the mailing list postings I read about it some time back.
:-) The details are really sketchy, and I don't have time to look at the code today (esp. since I'm on Solaris and I doubt it'd even compile).
Good thing this is not the real language. Cause I just looked at the test?.pasm files, and thought for a second (despite the name *.?asm) "Hey! This looks like assembler. How the hell can this be a step forward!?" But it is just a VM, and indeed it is sort of assembler language, but this is not what the end programmer sees.
The joke was about merging the syntax from the languages, but the real Parrot is about the VM. I think.
It's only perl - sure it should... "compile". Just did a quick runthrough myself....
TimC.
but the problem is, three-dollar crack has very little to no effect on the human memory.
He probably just forgot that.
When is someone going to implement that 100% data compression sysem I heard so much about around April time? I'm sure it would be very usefull! Just think about all the possibilities!
As a long time Perl zealot, I'd like to take this opportunity to vigorously protest this move. Posts on both Perl and Python mailing lists suggest that there *is* going to be some compromise at language syntax level to accomodate the common runtime. From the Perl perspective it's like "well, Perl 6 was going to be fully OO anyway, so what difference are going to make a few concession in syntax"? Well, I strongly object! I mean, I spent so much time learning Perl so I could be different and write cool obfuscated "Japh" sigs, and NOW they're going to make Perl look and feel just like every other C# on the planet? I've had it! If THAT's gonna get implemented, I vow to completely abandon my Monk robe and to only code in Visual Basic! Brother Monks, I urge you to join me in my protest so that the despicable traitor Larry Wall will see the error of his ways and will hopefully change his mind about this Frankensteinian abomination! United we will succeed!
:-)
ESR on encouraging the bytecode merge ( http://mail.python.org/pipermail/python-dev/2001-J uly/016406.html )
use.perl.org links ( http://use.perl.org/search.pl?topic=parrot )
$ ./test_prog t/test3.pbc
and i've got,
I reg 1 is 0
Segmentation fault (core dumped)
~/.signature
Parrot was an April Fools' gag.
/. editors consider this carefully next April. Otherwise we might have a story about Bill Gates & Bill Joy collaborating to produce a new proprietary rock-solid server GUI.
This is what happens when jokes go bad. I hope the
Windows + Sun = Greenhouse
Sheesh... Then someone will implement it...
I believe this is the low-level "assembly language" of the proposed new perl VM.
Perhaps, though, making a rock-solid Parrot-for-Palm would be a way to get a good implmentation of both languages for Palm. The developers could share with each other, and the OS-specific routines could be held in common (accessed via specific "header files" (modules, etc.)).
Hmmmmm....
I believe there was an April Fool's joke many years ago about a 16-bit version of the ARM processor called THUMB. But then only a relatively short time later ARM Ltd announced they were indeed working on a 16-bit frontend to the ARM (basically a new instruction decoder), and now the 'Thumb instruction decoder' is a standard part of many ARM family CPUs.
How many other things started out as an April Fool's day joke and then actually got implemented?
-- Ed Avis ed@membled.com
I think he called it Ruby.
The power of perl, without the inconsistency of perl. And shorter source code(from the great language shootout)
-- Make software not war
First we had TCP/IP over carrier pigeon (suggested
in an April fool's RFC). Now this... What next?
John_Chalisque
/. rarely makes me laugh, but that one was a great one. :) :)
Sorry, but what's the difference between this and a random bytecode/assembly language ? What's the point if neither Python nor Perl implementation are alpha'ed, too ?
I mean, how could we know if this is adequate for a python bytecode for example ?
Why not use an existing (Scheme/Lisp/Java) bytecode then ?
Besides, I'd be very happy if we could have a somewhat open, Free, standard bytecode. But why (I know there's a because) can't we use something existing ?
It's not dead yet. In fact, it's only just barely alive - so it's still barely capable of trying to gum you to death or to bleed all over you.
Some people just can't take a joke.
byroniverse
Okay, CMU-CL... and then someone writes a Dylan front end for it.
Eh, religious wars... Lisp is a good language, no doubt. It's one of the two or three oldest still in current use (does it in fact predate both Fortran and Cobol?), but all those parens...
/Brian
Just because someone started working on something intending to be a joke doesn't mean it's not a joke and that anything will come of it.
max
Simon Cozens, the Perl6 Pumpking, wrote that joke.
Life is like an egg better scrambled than fried. -- Ken Sawatari
The first FORTRAN compiler was written in 1954-57.
The first Lisp interpreter was written in 1958-59.
COBOL was started in 1959; the first specification was issued April, 1960 and it takes me more than 2 minutes to find whether a working implementation existed at the time, so you can do it yourself.
Visual Seasick will offer all the elegance and ease-of-use of C++, fused with the raw power and scalability of Visual Basic.
Analyst Larry Bribewell of the respected IT Research firm Rentrag Group, predicts big things for this de facto industry-standard language: "the first release, version 3.1, looks rock solid. We predict [0.8] it will overtake Parrot in quarterly revenue by Q1 2002."
(c) 2001, ZDnot.
I forgot what day it was. They laughed at me for believing in Parrot. They called me mad, but WHO'S MAD NOW?!?!??! MWAHAHAHAHA
Going out to google, a page or so down on this link resembles the chip sheet as I remember it. I'd have sworn I saw it in a mag and don't recall ever reading "Electronic Design".
I was hoping one of the other April fools jokes would have come true: Slashdot on FreeBSD 5.0
:)
Hmm... I guess that would mean FreeBSD 5.0 would need to be released
Success is as dangerous as failure, hope as hollow as fear.
There is no sense in which the languages will be merged. If moving to Parrot required a substantial change in Python it just wouldn't happen. If Python on Parrot was less efficient than the current Python interpreter, that would also be a major issue.
The one part of the spec that apparently has been implemented...
SPECIAL FEATURES
Because of the employment of the Signetics' proprietary Sanderson-Rabbet Channel the 25120 will provide 50% higher speed than you will obtain.
"Michael, I did nothing. I did absolutely nothing - and it was everything that I thought it could be."
At least the Java byte code is very specific to Java; it doesn't map well into other languages and specifically not well into dynamically typed languages like Perl and Python.
In CVS there's already a mini language (Jako) that can be compiled into Parrot assembler code.
- ask
--
ask bjoern hansen
- ask (cvs.perl.org maintainer).
--
ask bjoern hansen