VBer can't understand LINQ
-
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 still find it scary ".net developers" can't do both.
I'm largely language agnostic
After a while they all bug me :doh:
-
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 see the post about the VBer is closely related to your signature. :laugh:
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Microsoft MVP - Visual C++[^]
-
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
-
LINQ implemented syntactically and semantically in R6RS Scheme in 250 lines of code. View here[^]. Not hard :)
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)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 :)
-
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
Mark Nischalke wrote:
"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."
:omg: Maybe they ought to read this: LINQtoSQL_VB[^], though on the too much code only side for my likes.
"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
modified on Friday, July 18, 2008 12:01 PM
-
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
As I used to do both VB.NET and C# nearly everyday, I used to say that VB.NET or C# is really not matter for me.. I've been doing this for 4 years without any problems. but when I started doing LINQ, the syntax that we can use in VB.NET and C# are quite different.... Actually, it's not about LINQ. It's about the inconsistent feature of C# 3.0 and vb.net 9.0.. For example: I can use "var" in C# but not in VB.NET. I can directly assign the XML code to a variable in VB.NET but i can't do that in C#.. So, i think the developer won't be able to switch from C# to VB.NET so easily if C# team and VB.NET team keep on doing that way...
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
modified on Friday, July 18, 2008 12:21 PM
-
I still find it scary ".net developers" can't do both.
I'm largely language agnostic
After a while they all bug me :doh:
-
I still find it scary ".net developers" can't do both.
I'm largely language agnostic
After a while they all bug me :doh:
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
-
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 used it for about a month, no joke, and was writing code faster than I did in VB...
To be fair, you can replace C# with "x86 assembler" and have the same experience... :-\
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
-
Sam Rahimi wrote:
I used it for about a month, no joke, and was writing code faster than I did in VB...
To be fair, you can replace C# with "x86 assembler" and have the same experience... :-\
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
I don't know if a month of X86 assembler would have me writing apps more productively than using the .NET framework LOL :)
-
As I used to do both VB.NET and C# nearly everyday, I used to say that VB.NET or C# is really not matter for me.. I've been doing this for 4 years without any problems. but when I started doing LINQ, the syntax that we can use in VB.NET and C# are quite different.... Actually, it's not about LINQ. It's about the inconsistent feature of C# 3.0 and vb.net 9.0.. For example: I can use "var" in C# but not in VB.NET. I can directly assign the XML code to a variable in VB.NET but i can't do that in C#.. So, i think the developer won't be able to switch from C# to VB.NET so easily if C# team and VB.NET team keep on doing that way...
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
modified on Friday, July 18, 2008 12:21 PM
Michael Sync wrote:
in C# but not in C#.
You might want to fix that. :)
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
-
Michael Sync wrote:
in C# but not in C#.
You might want to fix that. :)
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
Big Daddy Farang wrote:
You might want to fix that
Oh! sorry.. :) fixed. Thanks a lot, man :)
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
I don't know if a month of X86 assembler would have me writing apps more productively than using the .NET framework LOL :)
Half-way joking, but... yeah. Last time i had to write a significant amount of VB it pretty much put me off coding altogether for a while. Wretched language... :rolleyes:
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
-
Michael Sync wrote:
in C# but not in C#.
You might want to fix that. :)
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
thanks. I'm not sure why my reply to your post goes to my own message. :(
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
thanks. I'm not sure why my reply to your post goes to my own message. :(
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
oh.. my reply that goes wrong move back to your message correctly.. everything looks like magic these days..
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
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
Let's not be too hard on VB, after all, VB is the gateway language. People start with VB and then move on to other languages.
“Cannot find REALITY.SYS...Universe Halted.” ~ God on phone with Microsoft Customer Support
-
Let's not be too hard on VB, after all, VB is the gateway language. People start with VB and then move on to other languages.
“Cannot find REALITY.SYS...Universe Halted.” ~ God on phone with Microsoft Customer Support
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
-
oh.. my reply that goes wrong move back to your message correctly.. everything looks like magic these days..
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
Michael Sync wrote:
everything looks like magic these days..
As it should be! :-D
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
-
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