Any decision to “scrap 1,600 lines of” anything at all is not something to be taken lightly. It's hard to make an economic justification for scrapping.
But I just finished chatting on the folks with some folks who are trying to figure out what it would take to re-deploy their existing massive PHP app to a portable-phone platform, and I basically had to say: “you're basically ‘on the wrong end of a sharp pointed threaded rod’ because all of your code is utterly and completely tied-in with your HTML.”
Precisely the characteristic that is most fundamental to PHP's explicitly-chosen design ... is now biting them in the donkey.
And it's really hard to think of “a five year old application” as now being “recalcitrant legacy code.” That's not much lifespan.
And that's quite an engineering concern. Food for thought, definitely.
-
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.
|
