Re: vb6 bcoming irrelevant?
- From: Bob O`Bob <filterbob@xxxxxxxxxxxxxxx>
- Date: Mon, 10 Jul 2006 09:18:54 -0700
MyndPhlyp wrote:
The general rationale used for obsolescing old products is the betterment of
future technology - getting rid of previous bad ideas in favor of presumably
superior ideas, trimming out dead wood rarely used to keep things "lean and
mean," etc. (How 'bout all those old Win3.x and DOS programs?) The bottom
line however is... well, the bottom line. Generating revenue and increasing
the profit margin.
Sometimes the world figures it out, and makes the necessary adjustments.
An acquaintance of mine recently bought a brand new Camaro.
Even though GM stopped making any some time ago.
Not restored, not refitted, not refurbished, not remanufactured.
A brand new **1969 model year** Camaro.
I believe that sooner or later, there *will be* a forward-looking product which
will give far more respect to existing VB6 code than anything we've seen from
MS to date. I won't care if it changes every single syntactical tweak MS ever
made to enhance plain BASIC, so long as code /just converts/
Bob
--
.
- Follow-Ups:
- Re: vb6 bcoming irrelevant?
- From: MikeB
- Re: vb6 bcoming irrelevant? (OT)
- From: MyndPhlyp
- Re: vb6 bcoming irrelevant?
- References:
- vb6 bcoming irrelevant?
- From: Darren
- Re: vb6 bcoming irrelevant?
- From: MyndPhlyp
- vb6 bcoming irrelevant?
- Prev by Date: Re: Cannot shutdown using this code and XP SP2
- Next by Date: Re: Mike: it's Working, more explanation Please.
- Previous by thread: Re: vb6 bcoming irrelevant?
- Next by thread: Re: vb6 bcoming irrelevant? (OT)
- Index(es):
Relevant Pages
|
Loading