I had the black screen problem a couple times, using Chrome. Then I fired up Firefox, and it was fine.
Why have 2 languages if they will only syntactically differ?
"Mmmh, i prefer curly braces to begin..end, well, I will pick C#!".
I don't see the point. What's interesting with different languages, is that they can teach you different things, you learn to pick the right one for the job, and you enrich your reasoning skills with new paradigms . Strangely enough, Luca himself agrees with that when he says that F# is good for a typical C# programmer because he will learn new things. Well, can the same be said for a VB programmer trying some C#? He won't learn anything, except maybe how to switch syntactic modes in his head.
And what about the cost of duplicating every feature? This maintaining of a VB team, a C# team, while it finally boils down to one product? Like Daniel Smith said, I really have doubts as to the size of the VB.NET community in comparison with the C# one. VB6 to VB.NET was such a huge step that many decided it was just as easy/difficult to go all the way to C#. To quote Luca, Microsoft body language was all C# in that time. VB .NET has been losing the battle from the start. Now, they say the 2 languages won't compete no more, but my guess is that this co-evolution is the best way to assure a very soon death for VB.NET.
Differenciation would have given it a chance, IMHO.
Jan 07, 2005 at 4:01PM
I totally agree with you that being so picky with syntax just doesn't seem right from a MS recruiter, as mean as a recruiter can be. And also, where would the program end? Because, not remembering HashTable syntax would lead me to write a hash table from scratch. There's simply no end to the stuff. Your XOR solution is so elegant, that I'm pretty sure the problem did actually specify that there was only 1 number repeated an odd number of times.