The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Your three options seem a little narrow and biased, exactly what you are accusing those who do not like VB.Net of being.
For me personally I do not like VB.Net as a language. It it far too verbose and has way too many keywords. For a number of years it lagged behind C# on supporting new features of .Net. And Microsoft should have never created the Visual Basic 6.0 Compatibility library. I prefer languages that have a statement terminator that is not a new line and just gravitated to C# because I come from a C-based background and enjoy its terseness.
Warning, I am using a broad stroke to generalize below and know that there are good and crappy programmers regardless of the language.
My biggest grip with VB.Net however is the type of developer that it tends to attract, that being people from pre-.Net VB. VB was never a very good language and didn't have good OO support. Putting a blob of procedural code in a Class file in VB6 seemed to be as object oriented as most pre.Net VB developers went.
The majority (again, not all) of VB.Net developers I have seen over the last 3 years or so haven't even put in the effort to learn the greatness and fullness of the .Net library, instead opting to use the Visual Basic 6.0 Compatibility library to hold their hand.
To me it seems languages such as VB and Cobol tend to attract someone who is more of a business person over a developer. The type of person who isn't as passionate about the technology and more about just getting a job done (there is nothing wrong with that). I am just the polar opposite; I am very passionate about the technology and always want to stay current (it provides for my family and I) as well as the overall quality of the final solution.
When you mix in the people who are passionate about the technology with those that are only interested in learning the minimum tools to get the job done you will get petty squabbles. This is nothing new and will continue in the IT departments around the world. The business-geek versus the uber-technology-geek.
VB.NET is the language that really got me interested in programming in the first place. I took a Java class and by the end of it I didn't really enjoy it that much and started to think that programming was not for me. Then I took a VB.NET course and everything changed. Programming was fun. I built good stuff with VB and was able to pick it up quickly. By the end of that class, I was in love with programming. Now I program mostly in C# and I actually prefer it over VB after having used both for a while. Regardless, VB is a real language that you can do anything you want in. Anyone saying otherwise is either clueless or just a jerk. There has been great stuff built with VB, for example The Ocean Framework[^].
Personally I am happy with visual basic and no longer care about other languages struggling to make their mark. If you have a good look at what is growing in momentum is SQL Server. It is now powered by visual studio the home of visual basic that houses the other languages through .net.
I believe that we will have to learn how to become DBA and learn SQL. If the power is given back to the DBA the only options coders will have are to drag a Data Object to a html 5 form and any code will just take away from what is supplied.
Microsoft SQL Server just another tool in VB Land.
Redundancy is another word for coders
Coders creating a service, coders creating forms to recreate the same code, who create code full of vulnerabilities and holes.
Why not make and set the rules on the server and drag and drop away?
I've pretty much only used vb6, vbscript and, of course, vb.net from 1.0 through 2.0. I've taken an extended break from doing any dev work and have been learning C# off and on for a few years now but haven't actually tried my hand in putting anything together.
I bacame frustrated as I observed fewer and fewer people writing coding tutorials and other examples with VB (including msdn magazine, as I once noted on here). I started to see that nearly everything being written and done was with C#. This trend has continued for several years now. It is because of this that I have decided that I will just switch over and move forward with C# even though everything I already know isn't C#. Without all those examples and how to's that are tremendously avail for C# but not so much with VB.NET (any longer), the choice for me has become more clear.
A number of times in the past when I was creating more complex project with VB.NET, I was unable to find the code/example/help I needed or I'd get some example written in C# that I was unable to convert properly (after using converters or asking for help in converting or trying it myself).
I've decided to move on from vb.net because .. it appears, most everyone else has (or everyone else that was providing code examples/articles/help).
I'm sure if we compare the number of new articles and code examples between the two, we'd see a massive, Massive gap.
Well, instead of acting like a gerbil, you could act like a lemming and jump off a cliff. Or, you could run to the nearest saloon and order as much beer as you can handle. Or, you could decide to go to bed because that was a stupid statement. When you die in the morning because the super-nova burned you to a crisp, you might have a split-second to think "Oh, I cudda had a V-8" (I hear its good for the hangover you might have had if you had time to have one.)
Kinda reminds me of the short-story where the moon was suddenly 10 times brighter. Everyone is enjoying the evening event except one guy who realizes right away this is his last night of life. Turned out half the planet died because of a superflare, not a nova and they were OK. Then the catastrophic weather killed everyone else, it just took a while to reach them. Real up-beat story.
Time and again we witness people desperately cross-posting the same query across multiple forums in the website. I trying to see if instead of reprimanding them why can't we have smart validation of 'similar'* messages posted by the same user in a 'specified'* time-frame.
* These can be configurable parameters based on user behavior and can be used as a valuable heuristic tool later.
And again I am not sure if this strategy would immediately befit as a site suggestion and hence initiating this brainstorming in Lounge.
Ive used a couple of the GoF pattens in my applications as well asread articles and books on them, i however want to find out from the rest of you guys where you used the patterns before?
So, if you could list examples or short descriptions where you have used the various Behavioral, Creational and Structural patterns inreal production applications that would be awesome!
Apologies for posting same thing in two places.
Christian mentioned that it would be better fitted in the lounge, thus me posting this general question here...
To be honest, I thougt it would make for a good discussion to see where people actually use te paterns in real business applications and their experience with it, but after reading some replies from the others i take it i am wrong.
Last Visit: 31-Dec-99 18:00 Last Update: 17-Aug-17 18:31