> masak made the offhand remark in #perl6 recently that I used as the > title of this message. Now that I'm done giving State of the Parrot > talks, I'm free to take off my optimist hat and realize that Parrot is > going to die a slow death if we don't do something drastic. I love the > vision that Parrot has, so as architect I want to do what's needed to > make it kick ass.
Hey guys; It is DakeDesu/KatrinaTheLamia ... uh--computers have stopped exploding, are in places where they will not get smash or stolen. Life is not the dangerous place it was before. I had not been able to check out the Parrot documenation until recently--I was going on the grounds that it kind of... well, wasn't what this currently is. It may be, that computer programmers are working on Parrot--and the documentation is reflecting that issue. Thus the answer is there... somewhere, if somebody figured they should write it down. (BTW: Larry Wall's design stuffs on Perl6 are much easier to navigate... that cannot be a good thing... just putting that out there) I am not really understanding the documents on what Parrot is suppose to be. Why am I "casting ruins" to figure out anything? Typically, the only languages I have to do that with are stuff like PHP, Perl5 and other silly bad designed languages (that is assuming they were designed and not a lump of other stuff, or attempts to be compatible with Perl4). Most of the stuff with Python, Perl 6 and other languages that seem to have a lot of thought around them, the documentation is easy to go through. Hell, Intercal, which is a joke for the most part--is at least "well" designed enough that I could easily go through the documentation to find whatever it is I am wondering about. It is "well" designed at being the worst design on the planet (which was its target). -=- There is a tutorial on the website for implementing a language called SQUAK... but I could not read it. I got to the part of using Regular Expressions to map the language, and I had some PTSD flash back to people trying to parse HTML with a set of REGEX... I woke up frothing, and something written on the wall in what looks like green blood of some weird summoning circle and the cryptic message "Don't <blink>! STOP IT!"... I figured further reading of the SQUAK tutorial was not a good idea. -=- Honestly, I think the main issue is the website http://parrot.org . It was on Google about three results down... Wikipedia was number one... a pdf was number two (I don't bother with PDFs), and number three was a blog post on Parrot.org ... this was when I saw it. Maybe if we organise our documentation in a way, that it is navigatable, simple, clean and concise... the problems may solve themselves for the most part here. I took this from the angle of looking into your stuff and asking, "if I wanted to make a third party workalike implementation, could I do this?"... and say what you will, Sun Microsystems and Microsoft have their stuff layed out easier to do a workalike (but, nobody WANTS to make a Windows workalike.. and it is hard to have this done in WINE/Cedega legally). Make jokes about Mr. Wall, the stuff on Perl6.org is much easier to go through and figure out what it is people are trying to do here with Parrot.Org. Yes--it may be an incorrect conclusion... but hey... that works better than this. Hell, going through the GNU info files on BASH programming seemed less like pulling teeth here guys. ~Katrina "DakeDesu" Payne The Harlot... who programs stuff.
