BQN community links

This page gathers links to work by the community. To get in touch, please use our chat forums.

There are a few repositories tagged BQN on Github, but also lots of BQN entries on these sites that encourage shorter-form programming:

See also:

Fan art

Wezl has provided a view into the BQN programmer in š¯•©e's typical place of residence.

Depiction, remodel, animation.

Links contain the encoded art, which is CC-BY 4.0: see the "setup JS" pane.

And razetime designed a desktop background based on the BQN logo and character set.

Can I help out?

Certainly! There are never enough hours in the day and contributors from beginner to advanced programmers are all welcome. If you're interested I recommend you ask on the forums first to get a feel for what exactly is needed.

You will certainly feel an urge to skip this paragraph and get to the fun stuff, but the most important resource for implementing a language is testing and the most valuable one for building a language community is accessible introductions to the language and learning materials. These are both very demanding, but if you're willing to put in the work to advance BQN in the most effective way then this is it.

Work on BQN's implementation generally requires a high level of programming skill. We're focusing development effort on CBQN (see this source overview). It's true that the entire compiler and a (decreasing) portion of the runtime is written in BQN, but it would be hard to do much with these as they are very nearly complete, and work satisfactorily. If you want to try out another new language, we're starting to use Singeli for primitive implementations because of its low-level control and extensible abstractions. And there's still work to do in C, particularly expanding system value coverage. We'd also be interested in bringing in typical compiler optimizations like dead code elimination, constant folding, and escape analysis. I'd expect the design of these features to be much like any other IR compilerā€”or less hard, as BQN is fairly strict about the way variables are used.

There's no need to work on our implementation! BQN's specification and tests are there to make sure you can write a conforming implementation, and extend it with your own ideas. It's also possible to take advantage of the self-hosted BQN sources by writing a virtual machine that allows you to embed BQN in the language of your choice.

Building libraries for BQN users can make writing programs in the language much more approachable. You are a better judge of which libraries are needed than I. Port some code from another language, implement some useful functionality in a field you specialize in, or try something new that interests you. A library should be structured as a file (which might load other files) that loads a namespace. This isn't too well-documented now, but see the namespace documentation for hints, and bqn-libs for my work-in-progress vision of what developing one should look like.

Those are possibilities, not limitations. The best contribution is the one that fixes something I didn't even know was wrong.