Pharo vs twinBASIC

In Pharo everything is an object. Compiler - object, network - object, method - also an object. And objects communicate with messages. No operators, no control-flow statements. Just objects and messages. Few things to learn, but you can learn OOP well.

There is good, free documentation including several books written by experts with extensive examples. There is an online MOOC. There are many tutorial videos. Supportive conferences and community. Even a professional support option if desired.

The nature of Pharo being a "live" environment allows you to perform live updates to your system without requiring to restart it. You can upgrade/modify classes while serving requests at the same time.

The framework for developing sophisticated web applications in Smalltalk is developed in Pharo. Seaside lets you build highly interactive web applications quickly, reusably and maintainably.

No need to search google for compact beautiful examples of how to do things, your live environment source is available and you can easily live search, see how it works and copy how the masters would do it (examples most languages still copy too).

Most languages are still copying the Smalltalk tools of yesterday - GTInspector (written in Glamorous) takes live exploration of code/running objects to a new level. It's really slick, and better yet, you can easily write your own inspectors in 10 lines of code.

Use 32 bit or 64 bit versions of Pharo on Windows, Mac & Linux.

MOOSE environment provides extensive, easily leveraged and class leading tools for code analysis and improvement.

Roassal and Mondrian provide fantastic and easily used frameworks for graphics, graphing and advanced visualisations (comparable to D3.js) but with much less code. Visualisations can be rendered into web friendly graphics (SVG, .png etc.) without additional work.

Any code that runs in VB6 will run in twinBASIC (once v1 is released). Code that runs in VBA will also run in twinBASIC, though you need to account for any dependencies on the host application's object model (e.g., the Excel or Access Application object).

The lack of a runtime dependency makes twinBASIC applications very lightweight and portable. Additionally, compiled executables only include necessary code from any referenced libraries. The classic "Hello, World" program compiles down to an 8 KB .exe with no external dependencies.

Can be used to extend VBA functionality by compiling standard and ActiveX DLLs in both 32 and 64bit.

64bit compilation is supported, as well as 32bit.

At last there is a replacement for Microsoft VB6 - and for VBA too - twinBASIC programming.