Re: Accelerated legacy code

Pete Dashwood <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Cydrome Leader wrote:
Pete Dashwood <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Howard Brazee wrote:
We tend to associate "legacy" with "mainframe". But it ain't
necessarily so.

From my limited exposure, the large new systems I have seen have
lots of code which doesn't fit new standards, but is kept around
because redesign and replacement is much more difficult when
anything can touch anything.

I'm calling it "accelerated legacy code".

I used to think "legacy" only applied to mainframe until I was given
a task to "keep legacy running while we develop and implement a new
solution" for a major Utility in the U.K.

heck, there can be legacy code and applications from even a few years
ago.

One example is a CRM/ticket system that only works with IE6. Users
can't even access it as the desktop build is beyond IE6. It simply
doesn't work, even with IE7 or IE8 in legacy mode. It doesn't work
with other browsers at all.


That's a pretty bad situation and a lesson to us all. I think most
responsible web developers check for at least SOME fundamental cross Browser
capability, or issue a disclaimer on their sites. With modern tools it isn't
TOO hard to check things across Browsers (although it is definitely extra
work)... 5 years ago such tools did exist (MacroMedia have had this
capability in Dreamweaver for more than 5 years, just as one example).

It's looking like some windows 98 machines will have to be kept on
hand to use the thing, and it the data on it has to be accessible for
X more years, even if nobody knows how to run it and it's on hardware
with no more support. It has to be less than 5 years old too.

I have to wonder why anyone would take delivery of such a system. I guess
they saw functionality they needed and decided the tech stuff didn't
matter...

I would have thought it would be pretty easy to replace a CRM system; there
are dozens of very good packages around that provide that functionality.

Well, I'm sure any "can" do what you need, but the big deal is setting it
up to do things the way business people want.

business folks aren't usually technical, and not always logical. That's
how junk like this is allowed to even be created in the first place.
.

Relevant Pages

  • Re: Accelerated legacy code
    ... I'm calling it "accelerated legacy code". ... One example is a CRM/ticket system that only works with IE6. ... TOO hard to check things across Browsers (although it is definitely extra ... Win98 machines around, ...
    (comp.lang.cobol)
  • Any need for addEventListener() and attachEvent() at all?
    ... Today I have been testing the event models from Netscape 4.8 and IE 4 ... libraries in YUI but it still seems to me to have some confused ... With all the new browsers I tested with this legacy workaround, ...
    (comp.lang.javascript)
  • Re: Accelerated legacy code
    ... I'm calling it "accelerated legacy code". ... TOO hard to check things across Browsers (although it is definitely extra ... capability in Dreamweaver for more than 5 years, ... are dozens of very good packages around that provide that functionality. ...
    (comp.lang.cobol)
  • Re: How to get the height of a td?
    ... Now it will not work in legacy 4.x browsers and fails in the WebTV/MSN TV views, so what are you testing with? ...
    (alt.html)
  • Re: Pythons simplicity philosophy
    ... >> personally argued that reduceshould be removed from the language, ... from legacy import * ... easy to get this functionality with a commandline switch, ... day-to-day python-dev traffic, but I don't think anything's been ...
    (comp.lang.python)