The problem with waiting is you never know how long that will be. The best thing to do is to start, and try to get others to help. You never need to do anything alone.

The thing to keep from having millions of templating toolkits or webmails and all, is the evolution of software. There is always a flood of solutions for a problem in software, but after a period of use the better ones survive and the rest fall away.

Also if you wait for someone else to solution something, you run the risk of having waited for a tool to still be dissappointed by what you you think are obvious missing features or un-needed features.

The responsible thing to do when faced with a problem is to find a solution. How you find a solutions depends on the problem. But usually researching the problem, researching the past solutions to that problem, and analyzing your needs in solving the problem, versus the solutions available. Than comes the hard part the decision on if you take the existing solutions as is, expand them or strike off in to new unchartered water.

My silly perspective is there are no unsolved problems, just problems that are not defined in a context where the existing solution is evident.

"No matter where you go, there you are." BB

In reply to Re: On waiting until a world becomes a better place... by Ninthwave
in thread On waiting until a world becomes a better place... by Eyck

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.