[stormdennis]

The whole point of TwinBasic is that it's to be 100% compatible with VB6 and with VBA.

From that standpoint there's no point comparing it with BBC Basic, Powerbasic, Freebasic, vb.net, purebasic, Xojo or gambas because none of those are in that space.

I'd like to hear more about who twinbasic expects to appeal to and why those people would want it?

[fafalone]

Well there's a small but significant community of hobbyists still using it for... we're enthusiastic about it to be subscribing already well it's still in beta to support it.

Lots of businesses still have critical line-of-business VB6 code and can't afford or have other issues with the total rewrite required to move anywhere else.

And one thing almost every commenter who thinks there's no market is overlooking: VBA. VBA is still huge in the business world. 64bit Office has become the default, but if you want to create active-x controls for it? Your options are... nothing without using a whole different language, usually C++. tB already has initial support for creating 64bit controls that can be used in Office VBA (and any other COM host including .NET, on top of being able to compile to 32bit for VB6 if so desired). There's a number of bugs to work out, but I've gotten some of my very complex controls running. Then you can also make VBE addins. All with the same VBAx64 syntax and language features you're used to with dozens of new ones.