Re: Not keeping backward compatibility.
From: Kirk Halgren (khalgren_at_sti.nasa.gov)
Date: 11/09/04
- Next message: QHenrick_Hellstr=F6m_=5BStreamSec=5D=22?=: "Re: Update on Who Owns the code"
- Previous message: Alexander Adam: "Re: Very interactive webapp"
- In reply to: Arjang: "Re: Not keeping backward compatibility."
- Next in thread: John Kaster (Borland): "Re: Not keeping backward compatibility."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 9 Nov 2004 10:55:57 -0500
"Arjang" <ArjangATmailDOTcom@NotTheRealPart.zorg> wrote in message
news:419062f1@newsgroups.borland.com...
> Hi Francisco,
>
> I didnot mean to say there is any problems, just that most of times trying
> to keep something
> backward compatibale stops it from being devloped more freely,
>
> Also have a look at this message:
>
http://www.codefez.com/Default.aspx?tabid=65&view=topic&forumid=9&postid=61
> and follow the links, you make up your mind as to wether it is worth it or
> not.
> I am not saying that it shouldnt be backward compatible, only was
wondering
> wether is it worthed by holding to the past to slow down the progess.
> Well it seems VCL will be carried into .net environment for some time to
> come.
>
> I didnt mean to make statement, but only a question.
> I am not qualified enough to decide wether it should be kept or not.
<snip>
ISTM that the difficulties involved in backward compatibility are related
directly to how well the architecture was thought out prior to writing the
previous version. I assume that Delphi has many fewer problems in this area
than other tools.
Early in my career I evaluated project management software, Microsoft
Project among them. Since we were already using Word (under DOS 3.3) I
decided to recommend Project because its user interface was the "same" as
Word. After we began using it we found that the interface wasn't really the
same. Tabbing worked differently, clicking with the mouse did also
(something about one version allowed clicking anywhere on a label or edit
box, the other ignored you if you clicked between the label and the edit
box, etc.) so they clearly weren't reusing the interface code. Just
different enough to drive you nuts if you tried to work quickly, based on
memorizing the user interface.
When data loss bugs surfaced, we switched away from Project.
Why not reuse that code? I never understood, other than the "I can't trust
anyone else's code" syndrome. That's no way to run a corporation.
If an ActiveX object's interface is to remain untouched forever, why not the
user interface too?
Kirk Halgren
"A large brain, like large government, may not be able to do simple things
in a simple way."
- Donald O. Hebb
- Next message: QHenrick_Hellstr=F6m_=5BStreamSec=5D=22?=: "Re: Update on Who Owns the code"
- Previous message: Alexander Adam: "Re: Very interactive webapp"
- In reply to: Arjang: "Re: Not keeping backward compatibility."
- Next in thread: John Kaster (Borland): "Re: Not keeping backward compatibility."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
