Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!feeder.news-service.com!xlned.com!feeder1.xlned.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!209.197.12.246.MISMATCH!nx02.iad01.newshosting.com!newshosting.com!69.16.185.16.MISMATCH!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!spln!extra.newsguy.com!newsp.newsguy.com!news2 From: Michael Wojcik Newsgroups: comp.lang.java.programmer Subject: Re: =?UTF-8?B?QW5kcm9pZOKAlFdoeSBEYWx2aWs/?= Date: Tue, 07 Jun 2011 12:09:12 -0400 Organization: Micro Focus Lines: 30 Message-ID: References: NNTP-Posting-Host: pa4d274b5bbd8becd7b4be8f23e747b38ab3848459d68faa7.newsdawg.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5091 Lawrence D'Oliveiro wrote: > In message , Joshua Cranmer wrote: > >> That those are the top 10 languages in some order is probably >> reasonable, if you include the use of Basic in Office macros and other >> light programming ... > > But do you count all the versions of VBA as one language? For example, > macros written for Microsoft Office 2003 do not so easily port to Office > 2007 or later. It looks like TIOBE lumps all languages with "Basic" in the name into their "(Visual) Basic" category. So that would include VB6, VB.NET, VBAs of every version, presumably VBScript, and even things like Realbasic, as well as any legacy BASICs that might show up in their data. I agree that's a pretty diverse group to consider a single language. While I avoid VB whenever possible, even I've seen enough to know that the move from VB6 to VB.NET included some major changes. (As it would have to; VB6 wasn't exactly a good fit for the CLR.) VB.NET is in many ways closer to C# than it is to historical BASIC. It's trivial to compile VB.NET into MSIL and then decompile it back into C#, or vice versa (if you avoid newer C# features that aren't supported in VB.NET yet). -- Michael Wojcik Micro Focus Rhetoric & Writing, Michigan State University