Is Visual Basic worth learning?

[Gook Nukem]

C# is easier than VB.NET in the sense that its syntax makes more sense in the end, with its C-like syntax.

VB.NET and C# are the same thing with a different syntax, pretty much

[Kogitsune]

[QUOTE=Quark:;32162362]C# is easier than VB.NET in the sense that its syntax makes more sense in the end, with its C-like syntax.[/QUOTE]

This is only true if you have previous experience with a C-style language and are already familiar with that.

[Dragonsdoom]

I'm gonna butt in here and point out that the [B]reason[/B] you are being taught VB is because it's still extremely commonly used in business applications.

It's sort of a vicious cycle:
VB starts as a 'learning' language.
New programmers learn it.
New programmers are taught other things, [B]in terms of VB.[/B]
New programmers graduate with a lot of experience relating things to VB.
VB becomes the easiest way for new programmers to correlate code to real terms.
Businesses hire new programmers.
Programmers program in VB.
New programmers grow to become current programmers.
Current programmers program in VB, so it's important that new programmers know how to use current systems.
goto 1.

Hence, many systems are still programmed in VB and it's important to learn so you can hold down a real job as a real programmer.

[BlkDucky]

[QUOTE=Dragonsdoom;32163492]I'm gonna butt in here and point out that the [B]reason[/B] you are being taught VB is because it's still extremely commonly used in business applications.

It's sort of a vicious cycle:
VB starts as a 'learning' language.
New programmers learn it.
New programmers are taught other things, [B]in terms of VB.[/B]
New programmers graduate with a lot of experience relating things to VB.
VB becomes the easiest way for new programmers to correlate code to real terms.
Businesses hire new programmers.
Programmers program in VB.
New programmers grow to become current programmers.
Current programmers program in VB, so it's important that new programmers know how to use current systems.
goto 1.

Hence, many systems are still programmed in VB and it's important to learn so you can hold down a real job as a real programmer.[/QUOTE]

Actually, C# is getting considerably more popular than VB.Net.

[Mr.T]

I learned VB without documentation during school hours, I removed the log off button for the XP computers so I actually preserved a computer for myself the whole school day. I also sent a net message to the head mistress saying that the computer had a virus, the whole school network had to close down for a day so the inexperienced computer tech could fix it. He said he removed the "virus". :v:

[Dragonsdoom]

[QUOTE=BlkDucky;32164584]Actually, C# is getting considerably more popular than VB.Net.[/QUOTE]

Indeed, so we should see schools begin to move away from VB in the near future. When I was leaving school this past summer they were talking about replacing Java with C# in the fall semester. Sadly, VB still remains as far as I know.

[Kogitsune]

[QUOTE=Dragonsdoom;32164891]Indeed, so we should see schools begin to move away from VB in the near future. When I was leaving school this past summer they were talking about replacing Java with C# in the fall semester. Sadly, VB still remains as far as I know.[/QUOTE]

I'd love to see an actually sound argument for why it's a "sad" thing that VB remains on the learning list.

[BlkDucky]

[QUOTE=Kogitsune;32165015]I'd love to see an actually sound argument for why it's a "sad" thing that VB remains on the learning list.[/QUOTE]

VB is completely and utterly irrelevant with C# on the scene. It has a completely different syntax to any other language and is (I believe) caps insensitive. It's possibly the worst language to start with considering there's nothing logical to follow on to because it's so different from anything else.

[Kogitsune]

[QUOTE=BlkDucky;32165051]VB is completely and utterly irrelevant with C# on the scene. It has a completely different syntax to any other language and is (I believe) caps insensitive. It's possibly the worst language to start with considering there's nothing logical to follow on to because it's so different from anything else.[/QUOTE]

The only case insensitive part about VB are variable names, which is a subjective "bad thing" since it prevents stupid mistakes like:

short someVal;

SomeVal = 123;

Everything else about the language is going to be case sensitive where it actually matters ( string comparison ).

It's different in syntax alone, and even then is extremely similar to C# since they both compile down to the same language.

NotInheritable = sealed
MustInherit = abstract
Overridable = virtual
Shared = static
Module = static class ( shorthand, all methods are considered to be static )

Those are just a couple - the language features are at near parity as well.

Consider the following code:

Module SomeModule
    Sub DebugMessageBox(ByVal msg As String)
#If DEBUG Then
        MessageBox.Show(msg, "DEBUG", MessageBoxButtons.OK, MessageBoxIcon.Information, MessageBoxDefaultButton.Button1, MessageBoxOptions.DefaultDesktopOnly, False)
#End If
    End Sub
End Module

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows.Forms;

namespace WindowsFormsApplication1
{
    static class SomeModule
    {
        public static void DebugMessageBox(string msg)
        {
#if DEBUG
            MessageBox.Show(msg, "DEBUG", MessageBoxButtons.OK, MessageBoxIcon.Information, MessageBoxDefaultButton.Button1);
#endif
        }
    }
}

Intellisense was fighting the overloads for Messagebox.Show, but the two extra arguments are still perfectly valid in C#.

The key differences are that all imported namespaces in the C# sample are project-wide references in a VB.Net winforms project.

Beyond that, both languages are extremely similar until you get to lambadas, which are just awkward as can be in VB currently, or if you desire to use the yield keyword, which doesn't exist in 3.5 although it might be in later versions.

Intellisense is mixed bag between the two - VB.Net will automatically show the contents of enums when they are an argument while C# does not ( although the enum object is the default selected object ), but it does get in the way sometimes when dealing with things like colors.

I can understand language preference, but disliking the syntax doesn't make the language a bad language.

[slayer20]

I talked to my teacher today about testing out of the class, and she said I was the first student to ever ask her that :v:

I got the name of the guy who teaches C#, Java, etc. and I'm going to shoot him an email to see if I can't set up some kind of private after-class study.

[Reagy]

Sure if you want to make a GUI interface to track an IP.

On a serious note though, if it's required to get into the C# class later on I'd go with it regardless.
If it's VB6.0 you'll just have to put up with learning a dimwitted outdated language which no one uses, if it's VB.Net it's somewhat useful.

[Gook Nukem]

[QUOTE=slayer20;32171005]I talked to my teacher today about testing out of the class, and she said I was the first student to ever ask her that :v:

I got the name of the guy who teaches C#, Java, etc. and I'm going to shoot him an email to see if I can't set up some kind of private after-class study.[/QUOTE]
The advantages to a private tutor are plentiful! You can ask more questions, you can get more help, and you can generally learn more.

[tyler3497]

Well I have to take a Visual Basic class to get into the AP Programming class, in which we learn java. I would have rather taught myself though, as everyone else in the class is extremely slow.

[slayer20]

So I asked around my school about C#/Java and I managed to get the email of the teacher who teaches that stuff. I basically told him what I plan on doing in life and what not (which is game design), and he pretty much told me he knows nothing about that sort of stuff.

The only game related class we have is about what businesses do when they come up the idea for games and what they go through to make it and release it.

I'm really not sure what I'm going to do now.