Re: Why does vb 6 seem to be getting more expensive?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Jul 31, 11:35 pm, "mayayana" <mayaXXy...@xxxxxxxxx> wrote:
They will break. Technically, they
are already broken since VB 5 is unsupported on Windows 7, and also
since I'm not willing to buy Vista (or any other MS products) so I can
test them to see if they are still working.

---------------------

    Can't you just ship the VB5 runtime? I feel
the same way in not wanting to keep giving
money to Microsoft, but you can still download
the DVD ISO for Win7 RC and it's supposed to
work until next spring.


Well, I just don't take the stuff that seriously. Be more fun to fire
up a new app :D


I've got it installed myself
for testing. Basic API code works fine. One drawback,
though, is that you need a pig of a machine to run
Win7. I recently switched my main PC from 256 MB
RAM to 512, though 256 was really plenty for Win98
and XP. No such luck with Win7. The basic OS
is about 9 times the size of XP (9 GB vs 1 GB) and
I think at least 2 GB RAM is recommended.


Yeah, I'm assuming my machine couldn't run win 7. Not enough RAM and
way too slow. I'm skeptical if it could even run xp.


  I find it somewhat odd that people talk so much
about broken compatibility. VB6 probably has the widest
compatibility of anything right now. And it's good



The problem isn't really broken compatability. Even if you choose not
to market a VB app to win 7 users, there's still a gazillion machines
capable of running it. The bigger problem is perception. I think this
whole episode has given VB a bad rep amongst the IT/techie crowd.
After all, if it was so great, so powerful, and so cutting edge why is
MS phasing it out? It must have been just a high powered toy! Trying
to sell a VB app to industry power users will likely get you laughed
at behind your back. You can target general users ("home users"), but
that's a much tougher audience to sell to. Also, you can bet MS and
company will do their best to encourage "end-users" to avoid software
that isn't .NET.



for at least 2-3 more years. Meanwhile .Net is just a
big package of wrapper objects that's going bonkers
with bloat, and Windows keeps getting worse. Will
.Net last longer than VB? That doesn't seem certain
to me.



I'm assuming the .NET runtimes will get bigger. I don't foresee them
shrinking. I remember an episode when we bought a USB device at radio
shack last year. It required the .net framework for the device
drivers. I downloaded it (took forever.) Then the installation
crashed after several minutes. I tried again. It downloaded the .net
framwork again. It crashed again. This is on an xp machine I might
add. Finally, after about an hour and a half of this, I gave up :D


  So what are we really losing with VB going unsupported?
I feel like VB is a canoe on a river that's drying up. It's
still usable and fun. The canoe won't become obsolete.
The river will just become unusable. That's a shame, to
my mind, but I don't feel like VB is being left behind.
There's not much left to be left behind from.


Well, this is computer programming. It's supposed to be hard work. If
you think vb.net is bad, spend some time studying Cobol. Ouch.
.

Relevant Pages

  • Re: not enough storage... error using GetRows
    ... > called the amount of RAM spiked to 550 MB RAM used, ... of a row in this data, to make a scientiffic estimate for memory consumption ... I am referencing ado 2.6 in the app but he has windows xp ...
    (microsoft.public.vb.database.ado)
  • Re: Can Someone Explain Something To Me?
    ... Mac apps load into RAM differently ... Mac presumes that you want to continue working with the same app, ... Windows assumes closing a document means you're done with the app. ... Windows' method makes the default behavior the one that causes delays. ...
    (comp.sys.mac.advocacy)
  • Re: Can Someone Explain Something To Me?
    ... Mac apps load into RAM differently ... Mac presumes that you want to continue working with the same app, ... Windows assumes closing a document means you're done with the app. ... Windows' method makes the default behavior the one that causes delays. ...
    (comp.sys.mac.advocacy)
  • Re: Can Someone Explain Something To Me?
    ... Mac apps load into RAM differently ... Mac presumes that you want to continue working with the same app, ... Windows' method makes the default behavior the one that causes delays. ...
    (comp.sys.mac.advocacy)
  • Solving the Blue Screen Of Death
    ... my Windows XP Pro installation started to experience ... eventually tracked it down to a faulty RAM stick (which had been fine ... Blue Screens of Death. ... The BSOD stop errors would vary (a lot of articles assume you always ...
    (microsoft.public.windowsxp.help_and_support)