|
Wow.
Dude. If you're going to say something like that, make sure you're exposed to more languages first.
|
|
|
|
|
6 years of school, granted my studies are out of date by 5 years
|
|
|
|
|
"with" isn't particularly unique or interesting.
There's a lot of functionality in a few lines. But you can stack up languages like cordwood that have lambdas, currying and/or templating features that would reduce the footprint of that code far more.
It's awesome to be excited about a language. Lord knows I've spent most of the last 40 years that way. But do yourself a favor, take this post and put it in a calendar item marked 5 years from now and come back and look at it then.
Visual Basic has come a long way since the VB3 days. But it's a very very long way away from winning awards for elegance.
|
|
|
|
|
The unique part about the with; is that it is simple - easy to learn, little if no problems to overcome just by using the structure.
|
|
|
|
|
Nothing against vb, but catching exceptions and then not handling them is epic fail for me, not "beauty and elegance".
|
|
|
|
|
Running through a database there are some times bad records.
I don't want them crashing the program nor do I care at this point what the problem is
|
|
|
|
|
It's just not that elegant to have two separate try/catch blocks that completely hide the error and never handle it. And everything you have there can be done in C# as well.
|
|
|
|
|
the try catches were not suppose to be illustrated as a bonus, and a laziness on my part, but intentional with how my code works
|
|
|
|
|
Actually it just got a lot more credit... Swift is Apple's version of VB. 
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
Swift looks like C# almost exactly
|
|
|
|
|
Of course my comment is tongue-in-cheek, but you must not have looked at Swift hard enough yet.
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
No I haven't, I've only seen declaring memory and other basic functions which all were the exact same as C#
|
|
|
|
|
As I frequently say - it's not the tool that is used that's the problem, but the tool that uses it.
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
That's why visual basic is great.
I don't need to hire anyone who thinks they are a programmer.
Its a tool that is easy to train people and allows me to pay them next to nothing.
|
|
|
|
|
Colborne_Greg wrote: allows me to pay them next to nothing
If you had written that from the beginning, I'm sure everone agreed.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
No, for the love of something NO! It makes writing code easier for those that don't write code. It only exists as some one else pointed out (probably) in reaction to Borland's Delphi (Object Pascal) MS needed to make there Basic compiler have similar features to compete! Bad programmers can write bad code in any language, the language makes it easier (VB) compare to another (C#) but they compile to the same byte code, you can't tell the difference! 
|
|
|
|
|
People that don't already write code are
-cheaper per hour
-easier to train
-get the job done faster
-get the job done without added flare
-almost half the cost overall as other programmers
-they write in full words (no bad habits)
|
|
|
|
|
also have no clue when something breaks...
I have seen VB programmers programming like they are chucking bricks over a wall!
|
|
|
|
|
Lmao indeed indeed
Gladly I am using Unidex and not SQL so the guess work for my programmers is next to nothing.
|
|
|
|
|
You hang on there my friend and protect our beloved language.
I used to be a VB.NET developer back in 2002 then I've seen the light (that would be C#), this is because I played with VB5 and VB6 during high school, because I played with QBasic during my early high school...
C# pays more and is more respected by developers and generally the code written in C# tends to be higher quality as the VB.NET code tends to be written by old school guys with less OOP experience than those of C# (I am saying "tends" not all).
Advice, move to C#
Make it simple, as simple as possible, but not simpler.
|
|
|
|
|
I think the OP needs some credit.. The intestinal fortitude required to even try to hold dialog favoring VB in anyway here is incredible. VB is my first language, partly because I've grown up my whole life under BASIC.. Partly because my first professional programming job was to convert VB6 to VB.NET and nearly every job since has required VB in one way or another. Who am I to question my employer on the politics of language? Who am I do judge my employer based on their chosen language?
I pulled the trigger and learned C# and have projects I still maintain. Its different, but it works and it makes me more marketable to be able to work in both. Right now, VB.NET is the required language and is what pays my bills. When it comes to new projects where language isn't a requirement I find that any classic WinForm or windows service projects stay in VB but I aim to use C# for anything else if possible.
Is C# still "the better language" if my code pattern mimics VB.NET concepts? Of course, regardless of right or wrong, it's still not VB. Is VB.NET any better of a language if my code pattern mimics C# concepts? Doubtful, because it's still VB.. I don't buy into this culture.
|
|
|
|
|
Visual basic 2013 is better then C#
|
|
|
|
|
Let us accept the fact that our whole logic is built around our natural language, that is the HUMAN language. Therefore, the programming language that is closer to the HUMAN language is more suitable for expressing algorithms. In other words, "IF... THEN... ELSE..." is far more clear and closer to the HUMAN language than if... {... }...
Prof. E. J. Yannakoudakis
|
|
|
|
|
Yes
also in C# there are two ways of writing an if statement such as
If something
do this result - only allows one line of code
if something
{ do this result} - allows multiple lies of code
if a coders places two lines of code in the first example the program fails...
|
|
|
|
|
RIP Eric Hill[^]
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
