Why move to C## ?
After making a case for writing code in VB with C++ programmers why would you move to C##? Is it as productive as you consider VB to be, and why?
C-double-sharp? Isn't that "D"?
The era of marketin gimmick languages is over. Don't bother to learn it. Learn what is already out there, that can build your application.
"Learn what is already out there, that can build your application"
If you believe building business software with beta tools is sane, you really are 'out there'!
It's not beta any more, you know.
Whatever - it's not 'out there'.
If I were going to start somebody off in coding, then the most important thing would be that the environment they would use is extremely interactive.
Why move to C#? To get a job as a sharp dressed janitor - that's my conclusion.
Remember "if you want to do buzzword programming, you must use a strongly hyped language"? Here's is an article seemingly intended as a self-realising prophecy: http://www.pbs.org/cringely/pulpit/pulpit20011101.html.
Joel - you need to change your script so that final periods won't be included in the URL. (I mean, Outlook and even Word can do this. :)
"." is a valid directory descriptor and is a perfectly valid ending charachter for a filename on every unix box I've ever used. Why shouldn't Joel allow it?
Try and click Andrzej's link . . . then you'll find out.
While it's perfectly valid, I can't name a single URL that ends in a period. The 99.99% of cases where including the period will mangle the URL are far more important than the 0.01% of cases where it's supposed to be there.
This question certainly has evoked some devastating wit. What's the matter guys, no Slashdot articles on Microsoft today, wherein to show off to all your buddies your stinging anti-Micro$oft repartee?
Period isn't the only character which may "brake" the legal URL - there are '?', ',', '!' and others ..
Fog Creek Home