A few more thoughts, after hearing some of the responses. In no particular order ...

There seem to be many different purposes put forward for the PerlmonksMoo.

None of those ideas are bad, on their face. In fact, they're all quite cool. And, frankly, are very unrelated to PerlMonks.

Games of any sort can be written and based on anything. Most of us don't have time to work on a game, even one based on PerlMonks. I personally read PerlMonks at work. I have a number of CPAN modules that have languished for lack of time outside work. I know I'm not the only one.

Tools to learn Perl are neat. But, what does a MOO have to do with Perl? MOOs are object-oriented - they're almost the poster-child for OO. Perl's OO (and functional) support are not pure. All you'd be teaching someone is how to use funny characters and a non-standard method-calling syntax. That would just be frustrating.

Kibbitzing with others ... now, this would be very cool. Except, you're now talking a true client-server architecture. I wouldn't want to build that website. MUDs and MOOs are either based on telnet or have their own clients. Either you require Java, write a cilent in JavaScript, or use telnet. Uhh ... I'm not thrilled by any of those choices.

Basically, while the current format is rough around the edges, it's been working for many years. Until the HTTP protocol is supplanted by something with state, that format isn't really going to change much.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested


In reply to Re: Perlmonks MOO by dragonchild
in thread Perlmonks MOO by Trag

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.