The VB Stigma - Good or bad, VB definitely carries a stigma in geek circles.With more choices, enterprise developers (motivated by factor two) my be opting for C# with visual developer support. Using Visual Studio no longer means that you have to use VB. Visual Tool Support - For the legions of enterprise programmers out there (the group largely associated with defaulting to VB, thanks largely to the era of pre-.NET Windows dev tools), the visual tools that once only existed for VB now exist for C#.I theorize that it may have to do with two primary factors: This is absolutely consistent with other indicators I've recently seen- from O'Reilly book sales trends to Telerik customer requests- that suggest VB's usage is on the decline. Over 60% of survey respondents indicate that C# is their primary programming language, about 34% VB, and a few people use J# or some other. Not because I'm ashamed of VB, but I finally realized how much syntactic overhead is involved in writing VB code. Needless to say, I've since migrated to programming primarily in C#. I liked VB, too, even in the face of my younger brother (a much more talented programmer than I, now headed-off to work in Redmond) ribbing me with the fact that VB was created "to enable dumb people to program." He may not have got that exactly correct, but VB's naming roots (and little else these days) are in BASIC, which stands for.anyone?." Beginner's All-purpose Symbolic Instruction Code." NET language: VB.NET felt right at home, C# looked like geek speak. Once I made the jump to ASP.NET, I had to choose a. My first real "programming" experience was as a web developer doing VBScript for ASP classic. Mention you're a VB programmer in a room full of geeks and your liable to earn the scoffs, smirks- if not outright insults- of the crowd. From the get go, I expected this survey to generate a lot of interest since the choice between VB and C# seems pseudo-religious.
Another survey and another set of interesting results.
0 kommentar(er)
