No Place for VB
-
Chris Maunder wrote: no VB6 articles. Why is that, Chris? I know that it's destined for the trash heap, but VB6 is still around and kicking, and VB.Net is not going to replace it anytime soon.
"Ask not for whom the bell tolls;
It tolls for thee..."We want to focus on Visual Studio .NET related content and unfortunately VB6 isn't supported. I understand that VB6 isn't going to die immediately but, well, do we really want to go there? ;) cheers, Chris Maunder
-
Not quite. I rejected a VB article and the author is unhappy. cheers, Chris Maunder
-
We want to focus on Visual Studio .NET related content and unfortunately VB6 isn't supported. I understand that VB6 isn't going to die immediately but, well, do we really want to go there? ;) cheers, Chris Maunder
Chris Maunder wrote: do we really want to go there? :laugh::laugh::laugh: That way madness lies... Still, it is a philosophical matter to consider. When I first joined CP, it was a valuable repository of information, a place to hang out with developers and other generally smart people, and a source of programming assistance focused on Microsoft tools. It still is, but VS.Net isn't taking the world by storm, and there's quite a lot of people still using VS6. It seems wrong to me to abandon them simply because they can't afford to buy Microsoft's tool du jure. CodeProject is still my Internet destination of choice, and long will be, but it's starting to look a bit like an online infomercial for Microsoft .Net products.:( I'd hate for anyone looking for help or wishing to contribute to feel that there's nothing for them here, VBers included.
"Ask not for whom the bell tolls;
It tolls for thee..." -
Richard Day wrote: Whats wrong with everyone and their dog thinking they can program? People will always need programming experts for the difficult stuff I want to work on, but the more crud that lesser mortals can deal with, the less ends up on my desk. Because somebody has to maintain that "crud" when the original progammer quits, gets fired, etc. I've already re-written 2 VB programs in C++ for this company (one small, one fairly substantial.) VB is a write-only language. If you want to do prototypes, throw-away code, or the like, VB is fine. VB is terrible for anything you need to maintain 5 year down the road. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein
Thats a fair point, but in the example you cite I am assuming you are talking about VB6 or earlier. The comparison between VB6 and C++ is pretty one sided. However, I would say that you can do some pretty goo stuff with VB6, but making it easy to expand and maintain is more the responsibility of the developer. The comparison between VB.NET and C#, in my opinion is a closer run thing. For any reasonably experienced programmer, learning the syntax of VB.NET, C# or any other language is probably less than a days work. The challenge is learning what the framework can do and how to do it! Once you've got that mastered you can use whatever language you like, and thats what I think is clever!