[ Previous entry: Binding to Internet Explorer Instances ]
[ Next entry: HEFTY Requirements ]
Just a quick quasi-rant.
Oh creative-and-innovative minds and fingers-pounding-the-keyboard influencing the human world... do place e.BackwardCompatibility beside e.Speed every time you re-design, recreate and develop things.
Ignoring it means two things (two for now... I'll mention the others later). One you're insulting the previous creators/developers/inventors and designers.
Not only that, you're also insulting the user.
Second, which can be connected or not to the first one, is... you've released a product that is not well planned, well organized and is not able anticipate future changes.
In this field of binaries, bits and data, one should design/create applications that are designed to last for decades, if not years. Something that should stand the test of time.
(And time is one cruel alpha/beta/omega/post-release tester.)
Now... I know there are always situations that are exceptions... and humans tend to move if not cross the line. This is where efficient and cumbersome conversion tools must come in.
Now the proponents of profit are shouting out the opposite of what I'm saying here.
Money-infested-and-blinded humans, I will talk to you later... that I will.
Disclaimers are for castrated EARTHLINGS.
Powered: GREYMatter | GM-RSS