it's much more fun than c++, but about the same as c#
it's much more fun than c++, but about the same as c#
That's understandable. I mean, it's just C# with dumb syntax that gives you RSI because You Have To Type So Much Code Just To Do Something Simple Because Visual Basic Dot Net Is So Verbose Full Stop Plus Comma Why Is Everything In Title Case Full Stop It Is Like A Really Long Book Title Full Stop.Originally Posted by Terrance
A little trivia: Did you know C# was originally going to be the only .NET language? The reason they added VB.NET was because there were soo many VB6 programmers who would have thought C# was too complicated (because of it's C++ style syntax) and not wanted to upgrade.
I love programming in VB.NET also. I don't mind that it's verbose. It's just fun, something I can't always say about c++.
The crows maintain that a single crow could destroy the heavens. Doubtless this is so. But it proves nothing against the heavens, for the heavens signify simply: the impossibility of crows.
Yeah, I guess everyone is entitled to their opinion (even if it is idiotic ).
C++ > VB6 > VB .NET
C++ is the most fun I've had since Python. VB was nice in that you could throw together something that looked pretty professional in an evening, but it's nowhere near as rewarding. C++ makes you think more (even if you're a guru).
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
That's exactly what I thought when I read his reply also. It's good to see that others here think the way I do.Yeah, I guess everyone is entitled to their opinion (even if it is idiotic ).
But I guess I was asking for trouble, on a c/c++ board singing the merits of VB.NET over c++.
Maybe it's because I haven't worked in a professional environment using VB.NET (and I'm sure there are issues there as well). But who hasn't had this experience before with c++: Some block of code, you didn't write it, has some annoying bug dealing with a pointer, heap memory, or maybe the stack and a buffer overrun that overwrites a return address. And you spend a week debugging this damn problem. You'll never get that 1 week back. And the killer is, the entire file (and the 10 other bugs in it that you haven't even found yet) is doing a less than optimal job of implementing some archane functionality, some minor detail that is given to you for free in .NET.
Don't get me wrong--I think c++ and c are GREAT for learning the details. It's just that if I am working for some company and I want to have a working, maintainable application in some reasonable period of time, I would choose VB.NET in a heartbeat over c or c++.
The crows maintain that a single crow could destroy the heavens. Doubtless this is so. But it proves nothing against the heavens, for the heavens signify simply: the impossibility of crows.
C# is not in consideration at all??Originally Posted by IfYouSaySo
source: compsci textbooks, cboard.cprogramming.com, world wide web, common sense
I just prefer the syntax of VB.NET to C#. For whatever reason, I like languages that are syntactically very different from each other. So my language choices are VB.NET, C++, and Python. None are very similar to each other. C# is too similar to c++ for my liking (same goes for Java). Just my preference...don't try to understand it. At any rate, C# is pretty much functionally similar to VB.NET, it's just a matter of which syntax you prefer.
The crows maintain that a single crow could destroy the heavens. Doubtless this is so. But it proves nothing against the heavens, for the heavens signify simply: the impossibility of crows.