If you show up and say "Hey, I have an idea for a new XML parser. What do you think of it?" Most of us will say, "Well, there are plenty of existing CPAN modules. So, why don't you wedge your idea in there?"

But, if you produce the clever code to fill a need not currently met, load it on CPAN, and meditate on the fabulous new way it works here and in other Perl places, people will thank you for your work. That's how XML::Twig came on the scene.

We like new ideas. But, we are a skeptical bunch. We have often heard people say, "I have a truly novel idea," only to find out that it was highly similar to existing work.

So, I say, "Try us." Write your module. Tell us how great it is. If it really works differently than the others, prepare to support a large number of users.

Phil

---

---

• 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.