|
I have nothing against VB,
but I'm afraid if efforts are being made to add a VB section,
the quality/quantity of the VC++ articles will decrement...
Keep this site as valuable as it is now
and don't start a VB section.
|
|
|
|
|
I started with Delphi and personal/politcal preferences aside, I think VB has its place. However, I don't think a section on coding in VB belongs here. I really don't want to wake up in the morning, rush excitedly to the computer, fire up my browser and see a bunch of "How to add a button to your form" articles. Don't get me wrong, everyone starts somewhere and adding a button to a form can be a daunting (yet rewarding) task the first time you do it.
The VB world is innundated with books, training and examples from Microsoft (something us C oriented guys could use), why add more garbage to the heap?
Ritch
PS- Ever notice how much VB improved after M'soft raped Borland's Delphi team? (Sorry, just can't let it go) 
Blah!
|
|
|
|
|
Maybe I'm not the norm, but I actually got my start in Basic (MS-Basic, then GW-Basic) before I got into C and then C++. Somewhere deep in my heart I've always wanted to see the language grow up and be recognized as a full professional language.
I think with the language equality that dot-net offers, this may be that time. For what it's worth, I'd love to see a VB.Net section on Codeproject.com. Even though I might not use it directly, I'd love to see how VB guys are approaching problems, and how the code is put together.
|
|
|
|
|
I started with BASIC as well ( AppleSoft, then goodness knows how many variations ), but I stil don't believe VB is relevant enough to enough C++ developers to justify it's presence here, as opposed to a sister site.
Christian
The content of this post is not necessarily the opinion of my yadda yadda yadda.
To understand recursion, we must first understand recursion.
|
|
|
|
|
VB is for people who don't wont to learn a proper programming language like C\C++  .
We don't want CP to turn into a VB site. There are hundreds of VB sites like CP (but obviosuly of no interest to proper programmers) we don't want another one.
Keep CP CPP 
|
|
|
|
|
That is an interesting attitude.
I take it that your the type of developer that picks the technology first then asks for the task details vs understanding the task then picking the appropriate technologies (and/or language) to do the best job.
Although I have been developing with C/C++ since the mid 80s, I use many other languages as well. Having a more broad scope on the advantage of different languages gives a great advantage when approaching new tasks.
|
|
|
|
|
Think it's not the attitude, but rather peacockery. So there is nothing to discuss here.
Regards,
Gennady
|
|
|
|
|
My programming language is better than your programming language ...
Because...
1. I only know one language
2. I only know how to approach a problem from one angle / one language scenario regardless of how easy / difficult it is to provide a solution
3. I'm a HaRdCoRe programmer / hacker who only looks at a problem in terms of 'x' languages features
4. Design ? that's for wimps who spend all day writing documents / diagrams and take ages to write any code.
Just a humble opinion from a C, C++, C#, VB, ASP, PHP, PERL, JAVA, VB.NET, Delphi, SmallTalk programmer.
It's not the tool, it's how you use it 
|
|
|
|
|
I agree with you on several points.
1/ It is better to be a programmer than a specialist in one language. If you're a programmer, then you program, and are able to apply that skill to whatever language necessary/
2/ Design is obviously important.
I disagree vehemently with the following assumptions inherent in your post.
1/ That being a programmer means you can do the job just as WELL with any language. A workman is as good as his tool, and VB isn't the tool that C++ is a lot of the time.
2/ The assumption that knowing only one language, and a complex one at that, means I don't know anything about design.
3/ That knowing a lot of languages is a substitute for knowing one or few *well*
4/ That language features are unimportant. I would *hate* to lose pointers, for example, because they are very useful if you know what you are doing.
Christian
The content of this post is not necessarily the opinion of my yadda yadda yadda.
To understand recursion, we must first understand recursion.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
