I cringe when hear things like "VB6-like" especially when used in conjunction with other platforms. Biggest question I'd have is the commitment these people have to the environment... or is it going to go the way of RealBASIC? Something that hasn't been updated in some time, and is still not up to the level of capabilities that VB had, and can't run ActiveX objects.
In fact, the forums say "This site was formerly run by Rohnny." ... which tells me it isn't anymore... and it doesn't look like there has been a release in close to a year. To me that's not good.
Hmmm... digging a little more, the forums seem active at least...
Meanwhile... there's also Mono, which is C# on Linux....
So take it for what it is... just be careful of projects that seem promising, but never quite take flight.
Gambas doesn't really work on windows, as far as I can see. And Mono is way too buggy.
But REALbasic is wonderful, — works well on windows,apple, and linux. It is actively updated, a new version about every 6 months. Its syntax is very VB6-like, (a clone, really), but with some new, added features. However, being cross-platform means that most COM won't work well with it. (although many activeX controls do work).
Another really good language is PureBasic, porducing fast, small exes. The comob of using REALbasic, Purebasic, and some VB6 is a winner!
Add to my above post: (the early versions of REALbasic were limited and buggy, but it's a lot different these days.) I like it.
The big problem with anything on the .NET platform is the code is easliy hacked. You can't protect yourself from pirates. Obfuscation is a joke, — there are many 1-click de-obfuscators. But machine code (like REALbasic or Purebasic) is much harder to crack. Hacker forums (which I visit to learn what they're up to), claim that VB6's p-code is the hardest of all for them to crack, although I don't completely understand this.
Really? A big part eh? So how is it that I managed to use VB6 for its entire lifespan and never once used mscomm ... it may be a big part to you... but it's not a major component of VB6 itself. VB6 itself still runs under Win7 ... some of the ancillary components may not how ever.
There are still so many number of applications around that were developed in VB 6. Some of the applications are big enough that even the rewriting costs will be higher, so it is a good idea to keep it going for more time.
Only one application running at a time??? That sounds pretty silly as many if not most of us will have more than one app running at a time and have more than one cpu in our systems. in my case I run 6 cores and more often than not have 3 or more apps running at once. One app at a time is fine on a phone but not on a workstation and what about the 100s of services that might need to be running?