The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
For my 60th birthday earlier this year I had a T-shirt made wiht the text:
"You don's have to be SENILE to be DEMENTED ... but it sure helps!"
(In Norwegian, as well in several other European languages, "senile" has been adopted as a short form of "senile dementia" in informal speech, although the "senile" means nothing but "old" - medical services classifies anyone of 60 years and older as senile.)
I did my first Basic programming as a high school exchange student in Minnesota: A huge Univac 1100 mainframe was set up in the Twin Cities, with 440 modems for use by 1500 schools all over the state. My school couldn't afford a "high speed" 300 bps modem; we had just a standard 110 bps one. But in those days, Basic provided only 286 numeric variables, named A-Z and A0-A9...Z0-Z9, and 26 strings named A$-Z$. So by character count, programs were small and compact!
I do see the point. There is no bloat, unless you explicitely put it in. C++ is multi paradigm: you may also use it effectively just as 'better C'.
As matter of fact I welcome the introduction of C++ in PIC32 microcontrollers code development.
Our principal application is almost 2 million lines of VB.Net. As a c# developer I was hesitant but it really is just about getting your head around a more verbose syntax and several months to break the semi-colon and curly braces habit! Wherever possible, I still prefer c# as it feels more grown up. The biggest issue is finding engineers willing to work with VB.Net - the second you mention VB the phone goes dead...
Keep your friends close. Keep Kill your enemies closer. The End
Nice flame war! A nice reminder of the VB shaming that exists here.
As a solo developer the choice between C# and VB is dependent on one thing only: Which one am I the most productive in? it all boils down to the same MSIL anyway and my clients don't care.
Now, back to the VB shaming. (since it's Saturday) It seems that haters will hate. The same old weak arguments regurgitated to prove why their beloved C# is superior and VB is trash and not worthy for serious work...or that programmers who prefer (or are stuck with) VB are inferior and should be scorned and ridiculed.
I think as a community, we can do better than to get all evangelical about something so petty. I don't have a dog in this fight...I like them both equally...just a tool to get a job done.