Some observations about our codebase:
- we still write new VB6 code where it is part of a larger project envir.
- we can drop some amount due to functionality not more in use
- so the total VB6 amount stays about the same.
- in rare situations only, legacy gets replaced by "actual paradigm work"
customer forces us to do so)
- quality of legacy code is abt same or slightly better than actual/new code
even if estimate mine & my coworkers proficiency better than 10 yrs ago.
we measure our efficiency/quality in lines to replace per 1000 lines total, where the customer does not have to pay for.
As such, its statistical importance is, like, way off the bottom of the chart.
That, and bananas are only red once they jump over the moon backwards on Tuesdays while it rains the color 9 as you listen to a green octagon being played by the letter J, who just had a birthday, by the way.
For an accepted error rate of 3%, you need the answer of some 1110 people with a "population" of 10,000,000.
See any decent documentation on "representative sample". E.g. How Many People Do I Need to Take My Survey?[^].
So, we are pretty good here, probably 2% error or less (I had to lookup the exact formula, though).
SURVEY SEYZ ~ Take an Anal-Rententive Suppression Pill
Freakin' criminey, man! SORRY for not including an emoticon EXPLICITLY INFERRING the post was non-serious.
Not that the post's info was of significance to the overall subject matter as something to *seriously* consider and contemplate upon in the first place nor that the info on bananas are only red once they jump over the moon backwards on Tuesdays... was entirely accurate.
Software people have changed the meaning of "legacy" - for the worse IMHO. Legacy used to mean something impressive, prominent and well respected. In software circles, it doesn't mean any of these things.
I completely agree with you! I have made beaucoup money working on legacy code.
Nothing is my fault, I always have an excuse (these days, the original developers are DEAD), and their only choice is to re-write a perfectly functioning system, even if clunky.
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
There are (according to Gartner research) 14 billion lines of VB6 programming still in use.
Who is going to rewrite that ?
The reality is that much legacy code will remain. If and when we get to the position that the software will not run (presumably on some future version of Windows, or when there is no longer a Windows desktop) then the users won't upgrade from their existing version of Windows.
With Visual Basic 6, most legacy programming is likely to remain in use on Windows or on VMs or on an emulator (WINE or whatever else becomes available).
Update or open source the VB6 programming language
It will fade away eventually.
I have a 30yr old piece of software I am replacing because it only runs on XP now (still DOS based).
But I noticed 2-3 other pieces of VB6 code that are no longer needed, specifically BECAUSE they are
moving away from that platform...
So, I will vote that some will be killed off, and much of it will die for a lack of need.
The great thing about good code, is that it should not have to change. Although, when
that really happens, people move to new, living software
It shouldn't be that Microsoft 'decides' everyone should re-write their software in a new Microsoft language every few years.
Now is the time for Microsoft to either update or open source the VB6 programming language ? Why won't they ? Perhaps they realize that updated VB6 programming would be more popular than their newer languages.
Last Visit: 31-Dec-99 18:00 Last Update: 4-Aug-15 15:24