Life after VB6

Since Microsoft has stopped supporting VB6, I think they should atleast make some of it open source. So we can redo somethings, add more features, and such. I know you can already do this by making your own controls and stuff, but having it directly in the program itself would be alot easier to work with. But, thats just my opinion.

Even though Micosoft has stopped supporting one of their wildly used languages, I dont think that it will stop being used ever. Its one of the most user-friendly programming languages, and its easy to learn.

Besides them dropping support of VB6, we still have places like this to look forward to to get support and feedback. Thats why communities like this are a real big help for programmers.

Theres tons of sites that help with VB6 and many other languages, so I dont think VB6 will ever become obsolete to use.

Just my 2 cents :D

I don't think vb6 will die that quickly either. I would like to make one point though - whatever language you use to program Windows (or any other GUI), you are only scripting! All 'visual' programming languages call pre-defined routines which, in the case of Windows, are written by Microsoft.

RealBasic is just another way of doing it and, given the evolution of VB, these early attempts are not bad. I have successfully converted a quite complicated drag and drop application and the associated Access database.

Wouldn't life be dull if we all agreed!

Not only is VB6 alive and well in the corporate community, it is still being widely used by commerical developers. My company makes and markets numerous commerical products, all written in VB6, maintained in VB6, and enhanced with VB6.

There are .NET versions in the works, but that does not mean the VB6 code will go away (unless, of course, that customers no longer wish to purchase that version.)

Quote:

---

Originally Posted by Oldschoolteacher

whatever language you use to program Windows (or any other GUI), you are only scripting! All 'visual' programming languages call pre-defined routines which, in the case of Windows, are written by Microsoft.

---

Isn't that the case for all languages and all OSs? In every language under every OS, you're bound to call something that's not build in the language and is only available as a system call. Even if you call fopen() in C, doesn't that call to the OS to do the work? After all, fopen doesn't have any clue about the details of the file system, whether that is Windows or Linux, and it must call to the OS.