comment on

I really do appreciate all those little and not so little innovations that make my life easier and enjoyable. Like my portable DVD player, which I use to see movies and tv series in bed.

I certainly see the pros and cons of imbedding the super search technology into the page for writing a new node. It's not just making it easier to write a good node. It's not just putting more of a strain on the servers of Perl Monks. It's not just behaviour. It's all this and much more.

If somebody doesn't want to read related nodes before posting a node, (s)he will not read the suggested related nodes.

If somebody does read the suggested related nodes, and use them to adapt his/her new node, the new node might become extremely detailed, complex, long, unreadable, and difficult to answer. Even when the node is already an answer to itself.

I think many monks would ignore this new proposed option.

In reply to Re^3: New node - Supersearch - Feature proposal ! by woolfy
in thread New node - Supersearch - Feature proposal ! by prad_intel

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks