VB.NET or C# 
Author Message
 VB.NET or C#

I am developing application only in VB for about 4 years.
I got the .NET beta 1 and I can see that I will have to learn all most a new
language if I want to use VB for .NET.

Is it better to learn C# or should I stay with VB ?

Thanks,
Asaf



Fri, 30 May 2003 18:42:09 GMT  
 VB.NET or C#
C# is the way to go. Visual Basic and Visual C++ are going to die at the end
of the road. C# is the future..

VB is for rookies, learn a decent language. C#, Delphi or Java



Sun, 01 Jun 2003 05:52:07 GMT  
 VB.NET or C#
Whatever. You're l33t, no doubt.


Quote:
> C# is the way to go. Visual Basic and Visual C++ are going to die at the
end
> of the road. C# is the future..

> VB is for rookies, learn a decent language. C#, Delphi or Java



Sun, 01 Jun 2003 06:13:44 GMT  
 VB.NET or C#

Quote:
> VB is for rookies, learn a decent language. C#, Delphi or Java

I agree, using semi-colons instead of enter makes it so much easier to
program.

Then there is the 'end' statements. As if "End Class" is that much clearer
than scrolling up and finding the matching bracket.

And who in their right mind would create a language that treated
DBConnection and dbconnection as the same variable? They are obviously
spelled differently. If I don't manually type the capitals, I don't want
some know-it-all IDE changing it for me.

Just look at how sloppy their switch statements are...
    Select Case X
        Case is <= 0
            //code
        Case 1, 3
            //code
        Case 2,  4 to 10
            //code
        Case Else
            //code
    End Select
Not only are they putting different values on one line, they are putting
whole ranges in a case. They aren't even using colons ( : ), let alone break
statements.

And don't get me started on the WithEvents syntax. If they are too lazy to
manually add and remove event handlers, they have no business programming.

Sure C# takes a lot more effort to get the same results as VB, but we can
say with pride that we worked hard to get to where we are. VB is just for
lazy programmers who care more about 'productivity' and "just getting the
job done" than elegance. They simply can't appreciate a well written program
with all the brackets lined up and all the event handlers correctly
registered.

--
Jonathan Allen
Typical C programmer


Quote:
> C# is the way to go. Visual Basic and Visual C++ are going to die at the
end
> of the road. C# is the future..

> VB is for rookies, learn a decent language. C#, Delphi or Java



Sun, 01 Jun 2003 06:50:24 GMT  
 VB.NET or C#
What?!?!

C# and C++ are for lazy programmers.  Every real programmer uses COBOL punch
cards.  Dah!

I mean common, a real programmer knows how to keep stacks and stacks of
cards in order for the machines to read.  People with keyboards and mice are
lazy.

-V-
Original COBOL Programmer


Quote:
> > VB is for rookies, learn a decent language. C#, Delphi or Java

> I agree, using semi-colons instead of enter makes it so much easier to
> program.

> Then there is the 'end' statements. As if "End Class" is that much clearer
> than scrolling up and finding the matching bracket.

> And who in their right mind would create a language that treated
> DBConnection and dbconnection as the same variable? They are obviously
> spelled differently. If I don't manually type the capitals, I don't want
> some know-it-all IDE changing it for me.

> Just look at how sloppy their switch statements are...
>     Select Case X
>         Case is <= 0
>             //code
>         Case 1, 3
>             //code
>         Case 2,  4 to 10
>             //code
>         Case Else
>             //code
>     End Select
> Not only are they putting different values on one line, they are putting
> whole ranges in a case. They aren't even using colons ( : ), let alone
break
> statements.

> And don't get me started on the WithEvents syntax. If they are too lazy to
> manually add and remove event handlers, they have no business programming.

> Sure C# takes a lot more effort to get the same results as VB, but we can
> say with pride that we worked hard to get to where we are. VB is just for
> lazy programmers who care more about 'productivity' and "just getting the
> job done" than elegance. They simply can't appreciate a well written
program
> with all the brackets lined up and all the event handlers correctly
> registered.

> --
> Jonathan Allen
> Typical C programmer



> > C# is the way to go. Visual Basic and Visual C++ are going to die at the
> end
> > of the road. C# is the future..

> > VB is for rookies, learn a decent language. C#, Delphi or Java



Sun, 01 Jun 2003 12:32:55 GMT  
 VB.NET or C#
I'm waiting for these guys who haven't seen anything but C++, C-sharp and a
tiny bit of VB to finally see something like APL.

Will they be impressed... APL code makes C++ code look like it's for
wusses... <bg>.

(apologies to APL fans, APL does avoid the prehistoric customs of C, like
curly braces to delimit everything!)

regards
Richard.



Sun, 01 Jun 2003 15:43:24 GMT  
 VB.NET or C#
I always thought fortran was the quintessential punch card language.

It's cool when something like...
If(a.gt.b)ThenC=5
... compiles. Much better than those verbose languages. Some actually
require spaces between tokens, talk about inefficient!

--
Jonathan Allen



Quote:
> What?!?!

> C# and C++ are for lazy programmers.  Every real programmer uses COBOL
punch
> cards.  Dah!

> I mean common, a real programmer knows how to keep stacks and stacks of
> cards in order for the machines to read.  People with keyboards and mice
are
> lazy.

> -V-
> Original COBOL Programmer



> > > VB is for rookies, learn a decent language. C#, Delphi or Java

> > I agree, using semi-colons instead of enter makes it so much easier to
> > program.

> > Then there is the 'end' statements. As if "End Class" is that much
clearer
> > than scrolling up and finding the matching bracket.

> > And who in their right mind would create a language that treated
> > DBConnection and dbconnection as the same variable? They are obviously
> > spelled differently. If I don't manually type the capitals, I don't want
> > some know-it-all IDE changing it for me.

> > Just look at how sloppy their switch statements are...
> >     Select Case X
> >         Case is <= 0
> >             //code
> >         Case 1, 3
> >             //code
> >         Case 2,  4 to 10
> >             //code
> >         Case Else
> >             //code
> >     End Select
> > Not only are they putting different values on one line, they are putting
> > whole ranges in a case. They aren't even using colons ( : ), let alone
> break
> > statements.

> > And don't get me started on the WithEvents syntax. If they are too lazy
to
> > manually add and remove event handlers, they have no business
programming.

> > Sure C# takes a lot more effort to get the same results as VB, but we
can
> > say with pride that we worked hard to get to where we are. VB is just
for
> > lazy programmers who care more about 'productivity' and "just getting
the
> > job done" than elegance. They simply can't appreciate a well written
> program
> > with all the brackets lined up and all the event handlers correctly
> > registered.

> > --
> > Jonathan Allen
> > Typical C programmer



> > > C# is the way to go. Visual Basic and Visual C++ are going to die at
the
> > end
> > > of the road. C# is the future..

> > > VB is for rookies, learn a decent language. C#, Delphi or Java



Sun, 01 Jun 2003 13:36:55 GMT  
 VB.NET or C#
I like my curly braces!  ;-)
Just an aquired taste I guess, kinda like broccoli, and liver!
<g>

Juan


Quote:
> I'm waiting for these guys who haven't seen anything but C++, C-sharp and
a
> tiny bit of VB to finally see something like APL.

> Will they be impressed... APL code makes C++ code look like it's for
> wusses... <bg>.

> (apologies to APL fans, APL does avoid the prehistoric customs of C, like
> curly braces to delimit everything!)

> regards
> Richard.



Sun, 01 Jun 2003 23:31:58 GMT  
 VB.NET or C#
Oh yeah?  I bet you people have never sat down with a pair of nitting
needles, ferrite beads, and wire to knit magnetic core memory modules.

Wusses.
-Dave


Quote:
> I like my curly braces!  ;-)
> Just an aquired taste I guess, kinda like broccoli, and liver!
> <g>

> Juan



> > I'm waiting for these guys who haven't seen anything but C++, C-sharp
and
> a
> > tiny bit of VB to finally see something like APL.

> > Will they be impressed... APL code makes C++ code look like it's for
> > wusses... <bg>.

> > (apologies to APL fans, APL does avoid the prehistoric customs of C,
like
> > curly braces to delimit everything!)

> > regards
> > Richard.



Sun, 29 Jun 2003 03:34:17 GMT  
 
 [ 9 post ] 

 Relevant Pages 

1. Convert VB.Net to C#, convert C# to VB.Net

2. Tell me you experience in convert code from VB 6 to VB.NET or C#

3. Eval function in VB .Net and C#

4. VB.NET versus C#

5. VB.NET or C# ?

6. VB.Net vs C#

7. VB.NET and C# mix

8. TCP/IP release renew in VB.net or C#

9. VB.Net or C# ????

10. Events and delegates in VB.NET and C#

11. VB.NET vs C# (again, sorry!)

12. VB.Net to C# translator

 

 
Powered by phpBB® Forum Software