Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Having read all the above posts let me offer my $0.02:

PerlMonks is slow but it's backed up by five years of development. Why throw all this away? Because it's slow. We've learnt a lot in five years and you can't tell me that there are no legacy remnants in the Everything code that are 'too embeded' to remove. Of course there are! Caching for one seems to be a problem.

Set the code free I keep hearing that there's problems that people will be looking at when they get the time, however why not make the source open so that we can all take a look? Surely the reason why most of contribute to open source is that if everyone can post a small change then we end up with a lot of goodness added. And before you all reply telling me that I can download the Everything source, let me make the point that the Perl Monk's source is very different from the Everything. Sure you can get a grasp on how it fundamentally works, but you can't write a MonkPatch.

Parallel Rewrite What I'd suggest is a parallel open-source rewrite. We colaboratively rewrite the Perl Monks site using everything we've learned in the last five years, starting with data design, then moving to data migration then onto the actual site. Don't think of this as 're-inventing the wheel' but as 'inventing the pneumatic tyre'.


In reply to Re: redesign everything engine? by BigLug
in thread redesign everything engine? by Jaap

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (8)
As of 2024-04-25 11:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found