I tried to learn VB.NET before C# and C++ and it was a disgrace. What the fuck does 'Dim' mean anyways? The keywords and everything else in C++ just makes a lot more sense to me. And this is coming from a guy who tried VB first.
[QUOTE=DeadKiller987;30536598]I tried to learn VB.NET before C# and C++ and it was a disgrace. [b]What the fuck does 'Dim' mean anyways?[/b] The keywords and everything else in C++ just makes a lot more sense to me. And this is coming from a guy who tried VB first.[/QUOTE]
"Dimension" I think. I'm just guessing.
[QUOTE=Fear_Fox;30536912]"Dimension" I think. I'm just guessing.[/QUOTE]
How does that translate to declaring integers?
I typed VB Dim into the magical world of google, and it told me that Dim was originally for arrays (dimension), but later became a declaration of any variable.
The wonders of the internets.
[QUOTE=yumi_cheese;30537728]I typed VB Dim into the magical world of google, and it told me that Dim was originally for arrays (dimension), but later became a declaration of any variable.
The wonders of the internets.[/QUOTE]
That makes sense actually. In a way.
I dislike it due to it's syntax being illogical/unnatural to me.
Back in grade 8, I always had Google/Help open to check if I was typing things right or using the correct "words" as I could never remember them. It was a pain to make even the simplest things. After we moved to Delphi in grade 9, everything felt so much more natural and it has been this way, mostly, for every language I've peeked into, narrowing down the problem to VB.
So much for being easier.
It's silly. People only think it's easier because it has words and not symbols.
I dislike it because it doesn't have semicolons. They're just natural to me. :(
It is a nice language for people making GUI programs though, I don't rip on people for using it, although I do notice the general quality of programs made with it is lower, just like any easy to use programming tool such as Game Maker compared to a harder language such as C++.
Visual Basic is ridiculed because it's syntax is so bloated it makes children cry.
Visual Basic was one of the first languages I learned... its good for rapid development of Windows form based applications. Once you get into anything more hardcore like games, it really shows its weaknesses. I still use it to this day at work. Whenever my boss asks me to make an application to do X & Y, I find myself using Visual Basic because its the quickest method of getting it done.
Any project I do at home, well lets just say I don't even have the Visual Basic IDE installed on my home computer.
For winforms applications, I find myself quickest in C#. I managed to (despite the fact that the code was messy as fuck) create a level editor for a top-down 2d shooter game in 2 days and it would export levels to XML (thank god for xsd.exe). That was about a month and a half before we had to release that game to the Android market.
I learned a bit of VB6. It was easy but so frustrating with the subs and dims...
At the end of the day as long as the language you're using doesn't compromise any elements of your program it doesn't matter.
I never really liked VB, but I was running some software I wrote at a FIRST Robotics Competition and needed a program to show the last created image in a folder. I managed to create it in two hours with (almost) no knowledge of the language and autocomplete. It was actually pretty effective. I didn't even know how to make a loop.
The reason I dislike it is because it's what kids learn these days in college and such (at least at my college). They all think they're god because they can make a button on a form that displays a message box.
[QUOTE=foszor;30546112]I still use it to this day at work. Whenever my boss asks me to make an application to do X & Y, I find myself using Visual Basic because its the quickest method of getting it done.[/QUOTE]
I don't really get this argument. You can be just as productive in C# as it's the exact same designer and class libraries but you don't have to deal with the clunky syntax
It's just like Game Maker. It's decent and works, but since it's easy there is bound to be a whole lot more of shitty things and 10 year olds showing off than say, C++ or C#.
[b]Edit:[/b] Oh shit. I didn't notice the date of the last post :geno:
Still a valid point though. People will mostly ridicule you if you do something the easy way.
[QUOTE=Xeon06;30554556]The reason I dislike it is because it's what kids learn these days in college and such (at least at my college). They all think they're god because they can make a button on a form that displays a message box.[/QUOTE]
This. I hate to see idiot twelve year-old kids talking in their completely and utterly obliterated microphone with their helium-like voice telling how to 'make a program that opens another program' in a 240p video where the colors are a soapy mess and smeared all over each frame of the video.
You can't see what they're typing in the code or what they're doing due to the production quality, your ears will beg the pain center of your brain for mercy and last - but not at all least - they are smug as fuck and think they're experienced programmers.
[QUOTE=tngr;30559369]I don't really get this argument. You can be just as productive in C# as it's the exact same designer and class libraries but you don't have to deal with the clunky syntax[/QUOTE]
Because I can't install or distribute any programs at work, I have to hide whatever I make inside an Office document (Excel, Access, etc). It sounds retarded but that's just how our IT department is.
[editline]30th June 2011[/editline]
BTW Office documents support something called VBScript, which is essentially Visual Basic... that's what I'm using.
This is why:
[url]http://thedailywtf.com/Articles/TransAtlantic-Time-Trap.aspx[/url]
[QUOTE=foszor;30796200]Because I can't install or distribute any programs at work, I have to hide whatever I make inside an Office document (Excel, Access, etc). It sounds retarded but that's just how our IT department is.
[editline]30th June 2011[/editline]
BTW Office documents support something called VBScript, which is essentially Visual Basic... that's what I'm using.[/QUOTE]You mean .vbs files? You can do that in notepad
[QUOTE=robmaister12;30491201]VB just doesn't look clean to me at all. I feel very unproductive in VB.NET just because of the bloat around it, if I want to define a variable:
"Dim myInt As Integer = 3" instead of just "int myInt = 3;"
If I want to use more than 1 line for a long command, I'd have to use _ at the end of each line in VB.
Having to explicitly state that you're ending an if or ending a sub just gets annoying, I can understand how that's supposed to prevent bugs where a mismatched set of { } would cause strange errors, but with just about any modern IDE, it'll highlight the other bracket for you, and if you tab correctly it shouldn't be much of an issue
But most of all I can't compress repetitive things on one line, namely switch case blocks (which I believe are select case blocks in VB.NET?).
[csharp]switch(someInt)
{
case 0: OneMethod(); someBool = false; break;
case 1: AnotherMethod(); someBool = false; break;
case 2: OppositeMethod(); someBool = true; break;
}[/csharp]
and again in VB.NET:
[csharp]Select Case someInt
Case 0
OneMethod()
someBool = false
Case 1
AnotherMethod()
someBool = false
Case 2
OppositeMethod()
someBool = true
End Select[/csharp][/QUOTE]
You can compress multiple statements into 1 line by using the : operator. [code]OppositeMethod() : somebool = true[/code]
[QUOTE=Within;30747487]This. I hate to see idiot twelve year-old kids talking in their completely and utterly obliterated microphone with their helium-like voice telling how to 'make a program that opens another program' in a 240p video where the colors are a soapy mess and smeared all over each frame of the video.
You can't see what they're typing in the code or what they're doing due to the production quality, your ears will beg the pain center of your brain for mercy and last - but not at all least - they are smug as fuck and think they're experienced programmers.[/QUOTE]
Google some IE5 exploit, there are thousands. Abuse that, and ???
Profit, ofc
VB is just... basic. It's better as a stepping stone to understand scope, functions, the whole shabang. C derived languages (I'm partial to C#, sorry) are just better because there's less fluff when you write.
And VB promotes lazy coders, because its just drag a gui element to a field then write a line or two of code.
[QUOTE=Huntsman;31037244]And VB promotes lazy coders, because its just drag a gui element to a field then write a line or two of code.[/QUOTE]
Errrm, thats not really lazy and thats just a gui designer.. Its not tied to VB
[QUOTE=Map in a box;31038568]Errrm, thats not really lazy and thats just a gui designer.. Its not tied to VB[/QUOTE]He means that you can plot an object onto the form designer and then code it in a line or two. It might be true, if you're setting an objects properties..I guess..
[QUOTE=Huntsman;31037244]And VB promotes lazy coders, because its just drag a gui element to a field then write a line or two of code.[/QUOTE]
That's Winforms, and it's available for all .NET languages. While there's a really nice editor for it that may initially seem simplistic, the winforms system is really in-depth and allows for control over just about every imaginable aspect of each control.
For example, I coded a simple level editor in 2 days. It would have taken double that amount of time (at least) if I didn't have available to me Panels and the Dock setting, where I would have had to code in everything by hand. On top of all that, each control uses .NET events, so that you don't have to write the same code over and over again for each different control. Because of that (and OpenTK's GLControl) I was able to quickly finish the work that would have been extremely tedious in a very short amount of time.
Oh and the PropertyGrid control is unbelievably useful for a level editor.
[editline]10th July 2011[/editline]
oh and if you feel like wasting some time, you can type out all your winforms code by hand. It's not in any way tied to the editor, but the editor makes it so much simpler and generates fairly clean code
[QUOTE=robmaister12;31040673]That's Winforms, and it's available for all .NET languages. While there's a really nice editor for it that may initially seem simplistic, the winforms system is really in-depth and allows for control over just about every imaginable aspect of each control.
For example, I coded a simple level editor in 2 days. It would have taken double that amount of time (at least) if I didn't have available to me Panels and the Dock setting, where I would have had to code in everything by hand. On top of all that, each control uses .NET events, so that you don't have to write the same code over and over again for each different control. Because of that (and OpenTK's GLControl) I was able to quickly finish the work that would have been extremely tedious in a very short amount of time.
Oh and the PropertyGrid control is unbelievably useful for a level editor.
[editline]10th July 2011[/editline]
oh and if you feel like wasting some time, you can type out all your winforms code by hand. It's not in any way tied to the editor, but the editor makes it so much simpler and generates fairly clean code[/QUOTE]
And i don't want to code it out by hand why?
I don't mind writing lines and lines,
Sorry, you need to Log In to post a reply to this thread.
