VisualWorks runs under many operating systems, including Windows, macOS, Linux, and several Unix versions.
For example, a graphical user interface (GUI) application needs to be developed only once, and can then be switched to different widget styles.
The various code browsers of VisualWorks help the developer to quickly locate a class or method of interest.
The performance and throughput of Smalltalk programs can approach the performance of static languages such as C++, Fortran, Pascal, or Ada using a just-in-time compiler by generating machine code that is specialised for frequently used types, but numeric processing and programs that benefit from precise memory layout may still run slower.
The generational garbage collector minimises most collection pauses, but may not be suitable for hard real-time and determinism requirements, as long full collections may occur, which may stop the world for tens to hundreds of milliseconds, proportional to heap size.
VisualWorks assumes a three-button mouse with buttons having logical names
These can be "filed in" to the VisualWorks IDE to generate any classes not already contained in the Smalltalk image.
The term components, in the VisualWorks sphere, is used to refer to parcels, packages, and bundles when it is not necessary to be specific.
When looking for code loaded from a parcel, one can locate the bundle or package with the same name in the System Browser.
The initial visual.im image contains minimal development facilities, using basic class libraries.
Additional class libraries are provided by VisualWorks or third-party vendors, usually as parcel files.
For most non-Smalltalk development environments, code libraries are imported at compile time, using an include command.
So even basic classes, like Object, differ from those in other Smalltalk-80 IDEs like Squeak and Dolphin Smalltalk.
In traditional object-oriented programming environments a developer directly edits a plain text source code file containing class and method definitions.
In browsing Smalltalk classes the developer gleans definitions from executing objects.
List panes in the System Browser allow developers to navigate to class and method definitions.
It illustrates how things like strings and files can be easily subsumed into the object structure within VisualWorks.