CBQN is the primary offline implementation, and has build instructions in its own repository. Here and elsewhere it's expected to be installed as
bqn. For Windows, build in WSL or go to the repository for the docker builds linked below (WinBQN is another system that's currently unmaintained).
Third-party packages are available for several platforms. Because they run on an unknown target system, none of these packages are built with the highest-performance settings. If you need top speed (you probably don't!) you should compile CBQN for the target hardware instead.
For tools related to running BQN, see the editor plugins and fonts page. Also, Beacon is a cross-platform IDE just for BQN!
|"Explain", error marker
|Preview, syntax coloring
|Coloring, images, audio
|Attempt This Online
|Do Stuff Online
|Many array languages
|For import in Observable
Both CBQN and JS BQN are implemented using components written in BQN itself: the compiler, and primitive implementations. The host language provides a bytecode VM and basic functionality for the primitives, and can replace primitives with native implementations for better performance. It also provides system values, so that which ones are supported depends on the host. This setup allows embedding, where programs in the host language can evaluate BQN code.
Support in the following languages has been implemented:
-e to execute all remaining arguments directly and print the results.
BQN.rkt is an independent implementation entirely in Racket, with primitives that operate on native Racket arrays (as these are multi-dimensional) and a compiler that converts from BQN to Racket syntax. It's incomplete as of this writing.
dzaima/BQN is an implementation in Java created by modifying the existing dzaima/APL, and should be easy to run on desktop Linux and Android. It was historically the main implementation, but is now updated only to stay up to date with language changes. Major missing functionality is dyadic Depth (
⚇) and set functions
⊐⊒∊⍷ with rank >1, and there are various small differences from the BQN spec, mostly to do with rank, handling of atoms, fills, and headers. It uses UTF-16 instead of UTF-32, so that characters like
𝕩 don't behave correctly.
The only remaining dzaima/BQN script here is
test/dzaima, which can be used to test the self-hosted primitives but has been superseded by