2 ms·
The main problem is the GUI Windows Forms that Visual Studio uses that they won't allow for use on other operating systems other than Windows. If they included
by orionblastar 12y ago
The main problem is the GUI Windows Forms that Visual Studio uses that they won't allow for use on other operating systems other than Windows.
If they included libraries that could compile the Windows GUI Forms to other operating systems like GNU/Linux, *BSD Unix, iOS, Android, Mac OSX ect it would be used more for those platforms.
Instead you have an incompatibility and it prevents developers on Non-Windows platforms to take it seriously. How can you claim it is cross platform when the GUI parts won't even compile?
Visual BASIC 6.0 was the last version of Visual BASIC that didn't stink and add in a bunch of Java features. I consider it Classic Visual BASIC for version 6.0 and under.
This Visual BASIC is really VB.Net and not Classic Visual BASIC. I'd much rather use the BASIC based Jabaco http://www.jabaco.org/ http://www.jabaco.org/ to make Java Bytecode JAR files than use VB.Net to make binaries. At least the Java JAR files are cross platform better than VB.Net and C#.
- dragonbonheur 12y agoThere is another BASIC that compiles to Java and is more actively developed than Jabaco :B4J http://www.basic4ppc.com/android/b4j.html http://www.basic4ppc.com/android/b4j.html Also for cross-platform development there are even dialects that compile to HTML+JS: http://pewtersoftware.com/browserbasic/ http://pewtersoftware.com/browserbasic/ And other platforms: http://www.monkey-x.com http://www.monkey-x.com
- orionblastar 12y agoThank you I'll look into them. Monkey-X looks like Blitz BASIC rather than Visual BASIC. But I like the fact that it can go cross platform.