Which do you prefer?

  • Thread starter Thread starter Master Programmer
  • Start date Start date
yeah like retarded VB.net wannabes.

I heard that VB.net is going away
even if it's not C# is 5 times as popular

-Aaron
 
What makes you persist eh?? LOL.

FYI: There are no other VB/VB.NET/.NET/whatever you refer to it as/VBA or C#
programmers in the entire company...

I heard that you were going away. Unfortunately someone made that up too.

To clarify: I'm a .NET programmer - not VB.NET - I don't import the
Microsoft.VisualBasic namespace.
If I want to use VB, I use VB6.
___________________________________
The Grimch
 
Anyone who has been working with .Net long enough should easily be able
to read both C# .NET and VB.NET anyway. If the code is written poorly
it won't matter whether it has Handles keywords or does all the hooks
by hand, it will still be bad code. Pick which flavor you like and get
rockin...
 
lick my nuts, Charlie

compatability with C# is NOT a benefit of VB

C# is a ****ing disease and the motherfucker who coninced MS to invent
a new language-- instead of taking VB 2002 seriously-- should be drawn
and quartered on live TV.

of course; it's a dead issue now.. C# has won the war... so now MS is
going to kill off VB.net sometime soon.

-Aaron
 
Totaly true, who the **** wants that other garbage to look at. Couldn't
have put it better myself Aaron.


The Grand Master
"When you have reached the top of the mountain
you can look down at everyone else."
 
You obviously don't do any async programming with .NET then?

If you don't know how to manage handlers yourself you will be in
trouble.

The Handles keyword is fine for wiring simple button click events.
Thats is the reason it is in VB and not C#

I think that is a little misleading... I mean your right, there is nothing
really equivalent to handles in C# (thank goodness), it doesn't mean that the
IDE won't automatically wire up events for you. You can just double click
your little button and get a default event handler just like you do in VB.NET
- the difference is that if at some point I want to change it a runtime I can
:)

Really, I find VB.NET's handling of events cumbersome. My main problem with
VB.NET isn't that its a basic style language - it's that it is to dang wordy
:) Oh, and it's case insensitive - drives me nuts! I like to be able to do
this:

public class TheClass
{
private int theInt;

public int TheInt
{
get { return this.theInt; }
set { this.theInt = value; }
}
}

In VB.NET, I have to resort to the dreaded underscore:

Public Class TheClass
Private _theInt As Integer

Public Property TheInt As Integer
Get
Return Me._theValue
End Get
Set
Me._theValue = Value
End Set
End Property
End Class

Blah, blah, blah. To much typing.
 
I use VB.NET BTW... and I wasn't talking about compatibility, I was
referring to readability. It's like any spoken language, they have the
same meaning just different symbols and words to get there. Who cares
if someone speaks German, Italian, or English? What matters is the
association the words represent. You can do the same thing in both
languages, who cares HOW you do it.
 
you can't do the same thing in VB.net.

it's not practical.

do you know why?? because C# already got critical mass.. and MS doesn't
give a shit about VB anymore

-Aaron
 
Tom,

Today I selected in a C# project 30 controls, I mistyped an 30 events where
created.

In VB.Net it is just selecting and deleting.

Try it in your most important C# project.

Cor
 
No code should EVER need one single comment if it is written properly.
It should be easy to follow without ANY explanation needed. If your
code needs comments to describe it then I suggest you go back to
school.

The Grand Master
 
While I always recommend adding comments, it might be true that in business
programming many comments are only there for "backup purposes." But not all
programming is of a business nature. I once worked at a company that was
developing a PowerPoint-type program for a non-Windows platform. The main
programmer was in his 50s and had something like two PhD's in advanced physics,
etc. He was coding algorithms for 3D slide-transition animations in his head.
Wow!

In one of the transitions, the user could enable a colored border around
the slide that was entering or leaving, a slide that was flipping this way
and that way. There was a bug in the transition that caused the border to
draw incorrectly at certain angles. Guess who's job it became to fix the
bug. (Me.) Guess who didn't add any comments to his source code. (Mr. Genius
PhD.) Guess who had a really hard time fixing the bug. (That would be me,
again.) I decided that day to never write a program devoid of comments.
 
I don't agree. I've written some really complicated programs
with complex statistical calculations, and I always put
in comments, if not for the poor guy who comes after me, then
for me 6 months later when I'm no longer working on it, and I
have to go back and fix it. It's been 2 years since I left
that software behind, and I still get e-mails thanking me for
documenting my code so well.

Robin S.
----------------------------------
 
Tim and Robin,

Do you know what is the trouble with me.

I can always better read code than even my own in any language written
comments.

Beside me I have seen that most developers are not given with rich
possibilities to write comments (and to tell something you can disagree with
me; I have seen that those who are able to write very nice comments often
make very bad code).

Just my thought,

:-)

Cor
 
Sir,

While I apprciate your forthright comment that you write code that ANYONE
can follow without any trouble at all, experience has taught me that the
only one that could possibly understand uncommented code is the person that
wrote that code. And if the person that wrote that code doesn't have a
photographic memory, it is very clear that they will not remember the
millions of lines of code that they wrote during their career.

I'm fairly new to programing, though I have been in the computer industry
for several years. I actually got to work on some uncommented code that had
been written in a language that had been 'extrapolated' from the C
programming language. Took me almost three weeks to fix the issue because I
had to 'learn' the language and then try to figure out what had been
written. If the code had been commented, the job may have taken me a lot
less time than it did.
 
I understand what you're saying. I'm not talking about comments
like this:

'define a variable to hold the count
Dim count as Integer

I'm talking about comments like this, that explain something out of
the ordinary, or explain *why* something is done a particular way:

'routine X seems like the logical place to put this instead
' of here in routine Y, but if you put it there instead of
' here, the dire consequences will be this
' (insert dire consequences). So even though this
' seems counterintuitive, don't move it. You'll regret it.
(seemingly oddly-placed code)

Robin S.
 
Why name it X or Y. Surely a variable named "loop_Counter" or
"array_Count" or "employee_Split" would be more intuative.

The Grand Master
 
Tom,

Today I selected in a C# project 30 controls, I mistyped an 30 events where
created.

I'm not sure what you mean here?
In VB.Net it is just selecting and deleting.

Try it in your most important C# project.

Yes, if you manually delete the methods, it can be fun manually deleting the
event handlers from initialize component. and your right, that doesn't happen
in VB.NET - but it happens so in frequently to me that I still see the C# way
of doing thing as a net advantage.

Don't get me wrong - I have no ill feelings against VB.NET. I just happen to
like C-style languages is all. It is what I have done most.
 
Robin,

Your particular comment suggest that the one who read it is able to
understand what you are saying.

In this case he needs some more than average knowledge of code to understand
why something is done. That one does not need your comment, he/she sees it
and thinks, whow I would not have done it that way, however according the
quality of the rest of the program the developer should have had a special
reason for that. Let me think twice and than probably sees the why.

For a beginner this kind of comments has no sense even with the comment they
don't understand it.

However again just my personal opinion.

In my opinion a good comment can be:
'See document xyz for an explanation of mathematics in the used code

Cor
 
I'm fairly new to programing, though I have been in the computer industry

That shows. Go off and spend a few years learning how to program then
come back with some useful comments. In the meantime shut your
cake-hole.

No-one wants to read a load of boring comments saying exactly what to
do with a piece of code. If the code is written properly then there
should not be any need to add "one single comment". Good code is easy
to read - bad code needs comments - end of story. Any statement to the
contrary is absolutly incorrect.

I find it disturbing that the language EVEN PERMITS you to add
comments. That is a feature that should be removed, thereby forcing
people to program properly, instead of being lazy-idle shites that
think they can add a bit of text to mask their inadequate skills.

The Grand Master
 
Back
Top