It's Official
-
Christian Graus wrote:
VB6 was an utter joke
I agree. I was introduced to VB3 back in 1995, took one look at it, and did not look at VB until VB.NET. Once I saw C#, any Java development I did, came to a screeching halt.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
Why'd you stop programming in Java? What turned you off?
-
Christian Graus wrote:
I mean, what can C# do better than VB.NET
C# can ease up the learning curve for people like me who grew up with C/C++ and Java. With VB.NET, I don't use it for any professional projects.
Christian Graus wrote:
the retarded syntax
Yep, but coming from a C/C++ background, I've managed to avoid the pitfalls of VB's syntax...
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
Paul Conrad wrote:
Christian Graus wrote: the retarded syntax Yep, but coming from a C/C++ background, I've managed to avoid the pitfalls of VB's syntax...
Coming from a VB background, I've managed to avoid the pitfalls of C/C++'s syntax... Employers pay for getting the product as quickly as possible more often than getting a product that runs marginally faster. Why should I reinvent the wheel every time and open my code to disastrous bugs such as memory leaks when I can get the job done faster without those pitfalls using VB? All programming languages are dangerous weapons... It is a matter of training the programmer to properly use them.
I don't claim to be a know it all, for I know that I am not...
I usually have an answer though.
-
Why'd you stop programming in Java? What turned you off?
wolfbinary wrote:
Why'd you stop programming in Java?
Found working with .NET better for business. More ease of use with C# and databases.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
Paul Conrad wrote:
Christian Graus wrote: the retarded syntax Yep, but coming from a C/C++ background, I've managed to avoid the pitfalls of VB's syntax...
Coming from a VB background, I've managed to avoid the pitfalls of C/C++'s syntax... Employers pay for getting the product as quickly as possible more often than getting a product that runs marginally faster. Why should I reinvent the wheel every time and open my code to disastrous bugs such as memory leaks when I can get the job done faster without those pitfalls using VB? All programming languages are dangerous weapons... It is a matter of training the programmer to properly use them.
I don't claim to be a know it all, for I know that I am not...
I usually have an answer though.
Scott Barbour wrote:
It is a matter of training the programmer to properly use them.
Exactly. I do teach a VB.NET course and one of the things I try to get across is good programming practice. It is not the language, but the user of the language. I've seen good and bad code written in practically all languages I've encountered in the past 27+ years I've been into programming.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
You've insulted my 2-slice toaster. At least it has multiple settings. ;P
Bar fomos edo pariyart gedeem, agreo eo dranem abal edyero eyrem kalm kareore
Yes but 7 of them leave you with burnt toast!
------------------------------------ Always acknowledge a fault. This will throw those in authority off their guard and give you an opportunity to commit more. Mark Twain
-
I despise VB, but there are definately good programmers who use it, I guess they learned it, got used to the retarded syntax and got good at it. I mean, what can C# do better than VB.NET, apart from 'be readable', and pointer access, which is something that's rarely needed ?
Christian Graus Driven to the arms of OSX by Vista.
Christian Graus wrote:
I despise VB, but there are definately good programmers who use it
I know good programmers who can use a hammer and a screwdriver really well, but that doesn't make those tools a programming language :laugh:
Learn from the mistakes of others, you may not live long enough to make them all yourself.
-
Paul Conrad wrote:
Christian Graus wrote: the retarded syntax Yep, but coming from a C/C++ background, I've managed to avoid the pitfalls of VB's syntax...
Coming from a VB background, I've managed to avoid the pitfalls of C/C++'s syntax... Employers pay for getting the product as quickly as possible more often than getting a product that runs marginally faster. Why should I reinvent the wheel every time and open my code to disastrous bugs such as memory leaks when I can get the job done faster without those pitfalls using VB? All programming languages are dangerous weapons... It is a matter of training the programmer to properly use them.
I don't claim to be a know it all, for I know that I am not...
I usually have an answer though.
I don't think you understood me at all.
Scott Barbour wrote:
Why should I reinvent the wheel every time and open my code to disastrous bugs such as memory leaks when I can get the job done faster without those pitfalls using VB?
Well, C++ programmers don't reinvent the wheel, nor do we suffer memory leaks that often, b/c we know how to code. I'm not sure how this remotely relates to anything I said tho. VB syntax is plain ugly to people used to elegant syntax. Syntax does not create memory leaks, poor code does.
Christian Graus Driven to the arms of OSX by Vista.
-
I don't think you understood me at all.
Scott Barbour wrote:
Why should I reinvent the wheel every time and open my code to disastrous bugs such as memory leaks when I can get the job done faster without those pitfalls using VB?
Well, C++ programmers don't reinvent the wheel, nor do we suffer memory leaks that often, b/c we know how to code. I'm not sure how this remotely relates to anything I said tho. VB syntax is plain ugly to people used to elegant syntax. Syntax does not create memory leaks, poor code does.
Christian Graus Driven to the arms of OSX by Vista.
Christian Graus wrote:
Syntax does not create memory leaks, poor code does.
Right on. This applies pretty much to any kind of tool out there. I am sure there are construction guys who could build a pretty crappy house with poor use of a hammer or nail gun.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
I despise VB, but there are definately good programmers who use it, I guess they learned it, got used to the retarded syntax and got good at it. I mean, what can C# do better than VB.NET, apart from 'be readable', and pointer access, which is something that's rarely needed ?
Christian Graus Driven to the arms of OSX by Vista.
Then have sympathy for us poor buggers who travelled the other path, started as excel macro writers (C64 doesn't count), side stepped into SuperBase (basic syntax), flirted with Delphi, got disgusted by 4GL stuff, even had a look under the hood of Notes and ended up with Access. The natural progression is to VB6/SQL Server and you end up in VB.Net. Now try changing to C#, and YOU think the vb syntax is screwy. As far as I'm concerned a pointer is a dog and I'm pleased to note they are rarely used in C#. I thought is would be simply a matter of learning a new syntax but there are a whole load of pitfalls in the differences between them. Still I have my utilities converted so at least I have the same tools and concepts.
Never underestimate the power of human stupidity RAH
-
John Simmons / outlaw programmer wrote:
it's a fact that VB instills bad programming habits
Name a few...
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
The main argument of VB-defenders is that nobody can blame the language itself since it's just a language. But, as sombody had already said, "by their fruits ye shall know". So I cannot "name a few" habits, but I can point at bad VB projects, and that is a special kind of bad which is specific to VB. :doh:
Greetings - Gajatko Portable.NET is part of DotGNU, a project to build a complete Free Software replacement for .NET - a system that truly belongs to the developers.
-
Scott Barbour wrote:
It is a matter of training the programmer to properly use them.
Exactly. I do teach a VB.NET course and one of the things I try to get across is good programming practice. It is not the language, but the user of the language. I've seen good and bad code written in practically all languages I've encountered in the past 27+ years I've been into programming.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
Well, I thought I was the one who said this. This clown seemed to suggest that because it's possible to leak memory in C++, VB is always better.
Christian Graus Driven to the arms of OSX by Vista.
-
Paul Conrad wrote:
Christian Graus wrote: the retarded syntax Yep, but coming from a C/C++ background, I've managed to avoid the pitfalls of VB's syntax...
Coming from a VB background, I've managed to avoid the pitfalls of C/C++'s syntax... Employers pay for getting the product as quickly as possible more often than getting a product that runs marginally faster. Why should I reinvent the wheel every time and open my code to disastrous bugs such as memory leaks when I can get the job done faster without those pitfalls using VB? All programming languages are dangerous weapons... It is a matter of training the programmer to properly use them.
I don't claim to be a know it all, for I know that I am not...
I usually have an answer though.
I also travelled this route and ended up in VB.net, LOB apps rarely care which language they are in and there is plenty of support out there for VB. Note most of the negatives are from C++/C backgrounds. I note you have 2 5s (not mine) there are a few VB lurkers out there happy to support your views.
Never underestimate the power of human stupidity RAH
-
Well, I thought I was the one who said this. This clown seemed to suggest that because it's possible to leak memory in C++, VB is always better.
Christian Graus Driven to the arms of OSX by Vista.
Christian Graus wrote:
seemed to suggest that because it's possible to leak memory in C++, VB is always better
As far as I know, and have seen, memory leaks can occur in both (pretty much most languages for that matter) when bad/sloppy programming practices are done.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
modified on Monday, December 1, 2008 7:45 PM
-
...
Christian Graus wrote:
there are definately good programmers who use it
...
Christian Graus wrote:
got used to the retarded syntax and got good at it.
ROTFL!!! So you mean there are good programmers who got good at using a retarded syntax? That should be a pain to be a good programmer and to have to look like a retard... (Teach yourself to be a moron in 21 days...) LMAO!! Ouark! :laugh: :laugh: :laugh:
No, I really meant that the syntax appears retarded to me, but that's b/c I learned C++ first and that's what seems natural to me. After C++, VB is too verbose and hard to read.
Christian Graus Driven to the arms of OSX by Vista.
-
Then have sympathy for us poor buggers who travelled the other path, started as excel macro writers (C64 doesn't count), side stepped into SuperBase (basic syntax), flirted with Delphi, got disgusted by 4GL stuff, even had a look under the hood of Notes and ended up with Access. The natural progression is to VB6/SQL Server and you end up in VB.Net. Now try changing to C#, and YOU think the vb syntax is screwy. As far as I'm concerned a pointer is a dog and I'm pleased to note they are rarely used in C#. I thought is would be simply a matter of learning a new syntax but there are a whole load of pitfalls in the differences between them. Still I have my utilities converted so at least I have the same tools and concepts.
Never underestimate the power of human stupidity RAH
Pointers are almost never used in C#, but the concept is really very simple, compared to what they could be used for in C++. My point was that whatever you're used to, is not screwy. C# makes perfect sense to me, VB does not.
Christian Graus Driven to the arms of OSX by Vista.
-
The main argument of VB-defenders is that nobody can blame the language itself since it's just a language. But, as sombody had already said, "by their fruits ye shall know". So I cannot "name a few" habits, but I can point at bad VB projects, and that is a special kind of bad which is specific to VB. :doh:
Greetings - Gajatko Portable.NET is part of DotGNU, a project to build a complete Free Software replacement for .NET - a system that truly belongs to the developers.
gajatko wrote:
So I cannot "name a few" habits
You can't name any specific bad habit?
gajatko wrote:
I can point at bad VB projects
Like-wise for any programming language out there. My point is not to blame the language but the person using the language. I've seen good, elegant code written in VB.NET, C#, PHP, Java, and likewise just as bad of code written in the same said languages by some clown who picked up a for dummies style book and tries to be a programmer overnight.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
Well, I thought I was the one who said this. This clown seemed to suggest that because it's possible to leak memory in C++, VB is always better.
Christian Graus Driven to the arms of OSX by Vista.
Christian Graus wrote:
VB is always better
CG you had to work hard to get that interpretation.
Never underestimate the power of human stupidity RAH
-
Pointers are almost never used in C#, but the concept is really very simple, compared to what they could be used for in C++. My point was that whatever you're used to, is not screwy. C# makes perfect sense to me, VB does not.
Christian Graus Driven to the arms of OSX by Vista.
I presume you don't use both, I'm converting and naturally find what I am used to much easier. I still have to settle on a consistent layout so my C# is particularly ugly :-D.
Never underestimate the power of human stupidity RAH
-
Then have sympathy for us poor buggers who travelled the other path, started as excel macro writers (C64 doesn't count), side stepped into SuperBase (basic syntax), flirted with Delphi, got disgusted by 4GL stuff, even had a look under the hood of Notes and ended up with Access. The natural progression is to VB6/SQL Server and you end up in VB.Net. Now try changing to C#, and YOU think the vb syntax is screwy. As far as I'm concerned a pointer is a dog and I'm pleased to note they are rarely used in C#. I thought is would be simply a matter of learning a new syntax but there are a whole load of pitfalls in the differences between them. Still I have my utilities converted so at least I have the same tools and concepts.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
C64 doesn't count
Hey, hey, hey, Commodore Basic was fine for its time :laugh:
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
I don't think you understood me at all.
Scott Barbour wrote:
Why should I reinvent the wheel every time and open my code to disastrous bugs such as memory leaks when I can get the job done faster without those pitfalls using VB?
Well, C++ programmers don't reinvent the wheel, nor do we suffer memory leaks that often, b/c we know how to code. I'm not sure how this remotely relates to anything I said tho. VB syntax is plain ugly to people used to elegant syntax. Syntax does not create memory leaks, poor code does.
Christian Graus Driven to the arms of OSX by Vista.
I consider descriptive syntax to be elegant. I know that I am not the only one that has looked at c/c++ code and asked "What kind of code block is this right curly brace ending?"
I don't claim to be a know it all, for I know that I am not...
I usually have an answer though.