Slashdot Mirror
Microsoft Remains Firm On Ending VB6 Support
An anonymous reader submits "CNet reports that
Microsoft is remaining firm an ending support for VB6, despite a petition
and many requests from its developer community.
If only VB were a F/OSS project instead of a proprietary customers could be assured of continued support as long as there was demand.
Are there any good F/OSS implementations of VB out there for customers to migrate to? One can only hope that enlightened groups like
the Agility Alliance would warn about the risks of using such software that can be end-of-lifed even while they're in heavy use."
My business still develops with the Visual Studio 6 tools and we refuse to switch to the .NET framework because of its large and expensive infrastructure. This is the same company that encourages high school students to become software engineers?? Microsoft..... what total assholes.
If you support Microsoft feel free to mod me down.
Delphi offers these same benefits. Let's face it. The reason VB is so popular is because Microsoft is its mother.
I applaud you for supporting the language you love. I am not a Visual Basic programmer myself, but I know that it has a place in the world, a place that is not filled by a more complex and more formal language. There are things you wouldn't want to write in VB, true, but that doesn't make a language useless. Just like a more conventional scripting language VB allows the creation of tools at minimal programmer expense. Why code up an app from scratch in days when you can do it for a few hours in VB. Especially when the app is light weight or in-house VB can easily outshine other languages. While VB may be coming to an end of it's lifespan it will leave a hole in a programmer's tool box that will eventually need to be filled by something else, something not currently available.
Philosophy.
Lets play smack the VB FUD down:) For the record: I've used Visual Basic professionally (complete end to end application work) along with Java, Perl, Python, and C++. Having in depth experience with all of those languages gives me good perspective on this particular debate (I think anyways:) ).
It is faster to develop an application in VB than any other language
Is it REALLY? This really needs to be backed up with research. I would argue that building MEANINGFUL applications would be accomplished much more efficiently in a language such as Ruby or Python (my prototyping language of choice) or even Java. You did not build a web-browser in 4 hours, you merely wrapped an existing one in a new interface. You did not build an e-mail client, you patched together some API's. This same magic is perfectly accomplishable in a number of other languages.
Visual Basic is more secure as a language
How is it more secure then Java or any other similiarly sandboxed language? As has been pointed out, your simply moving the security onus to code completely out of your control produced by a company with a spotty security record.
You earn more money using VB
That's rather situation dependent. I am a technical architect for a Symbian applications company (C++). There are relatively few people in the whole of the United States qualified to do my job and as such I'm compensated quite well. I make far more doing this than I would as a senior VB developer.
Saying that 'they almost always go with Visual Basic for the client and Java for the servers' is absolutely unbeleivable FUD. I've run across more CLI mainframe programs running against COBOL servers than possibly anything. New development seems to be more about web apps (some combination of Java/JSP generally). Visual basic seems to have a rather limited prescence in my experience. YMMV.
VB is a fine tool for what it is designed to do. As a language it leaves quite a bit to be desired. I find the syntax to be rather clumsy and I find that for significantly complex jobs it's simply not the right tool. It's definitely not a be-all-end-all that so many VB zealots like to make it out to be.
Turn s60 photos into awesome videos with mScrapbook for all S60 3rd edition phones!
For points 1,2 and (possibly) 3 see C#
The only reason anyone should be using VB is to maintain existing products. Any new products where VB was considered, should be using C# instead.
C# was thought to be MS's answer to Java. But what it actually did was remove any reason for VB to continue to exist. It wasn't the Java killer. It was the VB killer.
Any coder who can only code in a single lanaguge is a weak coder of no value to a company. At my job I've used at least 5 languages since I started. Times change, languages change. You need to adapt or you'll become obsolete.
I've used VB in the past. I used C# for a project having no knowledge of C# previously and instantly picked it up. I even managed to convert Quadpack from C to C# with little effort while putting up a nice GUI with the amount of ease that I was used to with VB.
VB is dead, switch to C#.
Work Safe Porn
Of course, you could say all the same things about Python with the added bonus of being Free.
So what does it mean if they no longer support it. Does it mean that you can't develop in VB6 anymore? Of course not. Does it mean you can't call them up and ask them questions about VB6? I don't know of any developer that would call up Microsoft to ask them a question about VB6. If they have questions, they check out newgroups and mailing lists just like F/OSS developers do.
Really the only thing that will change is that Microsoft will no longer release bug fixes. When was the last time you downloaded a bug fix for VB6 anyway? If you have functioning legacy software that uses VB6 then bug fixes probably aren't needed. If you're going to develop something new, you still have the option of using VB6 or you can use the latest and greatest development tools/language.
I fail to see the difference between this and an F/OSS project that's abandoned by its maintainer, especially those that are waning in their usefulness.
www.joshferguson.org