VBer can't understand LINQ
-
I agree that you should be able to read both. As for using them both, you should also, however, I've found I'm more proficient in C#
only two letters away from being an asset
Mark Nischalke wrote:
I've found I'm more proficient in C#
i agree. i have been able to hack into alien computers i never could have with VB. ;P hopefully you read the article a few posts up before you read this...
----------------------------------------------------------- "When I first saw it, I just thought that you really, really enjoyed programming in java." - Leslie Sanford
-
Not being hard on VB. Just found it humorous that the guy appeared to be totally lost when semi-colons were involved :)
only two letters away from being an asset
Mark Nischalke wrote:
the guy appeared to be totally lost when semi-colons were involved
He needs to be introduced to Lisp and all the ( ) then :rolleyes:
"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 being hard on VB. Just found it humorous that the guy appeared to be totally lost when semi-colons were involved :)
only two letters away from being an asset
-
Not being hard on VB. Just found it humorous that the guy appeared to be totally lost when semi-colons were involved :)
only two letters away from being an asset
Mark Nischalke wrote:
Not being hard on VB.
You're right, I didn't pay close enough attention before opening my big mouth.
“Cannot find REALITY.SYS...Universe Halted.” ~ God on phone with Microsoft Customer Support
-
C# seems scary if you come from VBLand, like I did... I used it for about a month, no joke, and was writing code faster than I did in VB... I'd advise everyone to switch over. In my personal, biased opinion :)
Sam Rahimi wrote:
I'd advise everyone to switch over. In my personal, biased opinion
I go back and forth without much of a hiccup. I've found that because VB is more verbose, it's easier to maintain which is a point in its favor IMHO, but usually its the shop that decides not the hired gun. Unless one wants and has long-term job security, not being able to write both is, again imho, like a man with one leg trying to ride a bike.
Jon Smith & Wesson: The original point and click interface
-
I still find it scary ".net developers" can't do both.
I'm largely language agnostic
After a while they all bug me :doh:
MidwestLimey wrote:
I still find it scary ".net developers" can't won't do both.
That covers the C# developers :)
-
I was searching around for books and checking the comments and found this one to be humorous. "It would be nice to have an author approach LINQ from a VB programming point. I really don't want to have to rewrite everything into C# just because no one seems to want to publish a book on LINQ using VB." http://www.amazon.com/review/R1MZ6Z4KBFP5BV/ref=cm_cr_dp_cmt?%5Fencoding=UTF8&ASIN=0735624003&nodeID=283155#wasThisHelpful[^]
only two letters away from being an asset
I find this humorous because, every time I try to find a solution on MSDN for a C# project, it returns a VB example as a response.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
