Quote:
Originally Posted by kyleb
I don't particularly like "what language should I learn" debates but in this case it's C# not close. That said, don't limit yourself to these language just because you think they are good. A sports simulator might be better written in a lightweight scripting language and heavy database use. (I've written similar programs in PHP/Perl/Python and MySQL)
I wince seeing Python put next to those other two, but I agree: everything should be first written in the "highest level" (read: most powerful) language available.
If it then turns out that certain parts are slow and often-run, creating a bad botteleneck for the whole thing, well, then you optimize those parts. But even then you fix algorithms first, and only then re-writing in another language if you must. But just the slow *and* often run parts.
Of course, to my knowledge this isn't really a concern for C# vs VB.Net, as I believe they're compiling with similar technology to the same VM.
BUT, there is an ocean of languages out there. All depends on OP's goal. If it's purely to pick up a language useful as part of some corporate development team, well, then learning both may be good. Probably C# first to get the more usual syntax, then learn VB's quirks.
If OP's goal is just to write software, though, there have to be better choices. *searches* Python and Ruby of course. If OP just wants to write software for the .NET system, then IronPython is out there.