As always, I am very thankful for the information and for your insights.

You personally may have no need for any of this, but rolling your own framework us unlikely to be as scalable or easily adoptable for others, which is important given the context of the discussion

Yes exactly. I run a small company where our websites are an integral part of what we do but are not our core business. We have half a dozen different sites which use common code for dealing with all the grunt work of what we need to do - decypher form data, check session cookies, encode passwords, send emails, upload files, etc. Each site generally has subroutines to produce the common parts of the page such as the header, footer, standard Javascript, CSS, etc and then there is a bespoke lump of code that does whatever that page is supposed to do.
For this, I really do not see any need for a framework and certainly nothing to be gained from converting existing code to utilise a framework.

But, I am the only person maintaining my code...nobody else needs to understand it or contribute to it. Having said that, I plan to employ a developer soon to free up some of my time and I'm aware they need to have some clues of what each bit of code is supposed to do. I think everything is adequately commented to give them a starting point!

Whilst I sort of see the benefits of utilising a framework, it still strikes me that it also has the effect of an anchor on development. If, as you say, the reason this site looks and operates like something from several decades ago is because of the framework being used, that is hardly a good promotion.

In reply to Re^8: Emailing Passwords? In 2020? by Bod
in thread Emailing Passwords? In 2020? by punklrokk

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.