aboutsummaryrefslogtreecommitdiff
path: root/commentary/stability.md
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2021-09-28 20:16:31 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2021-09-28 20:16:31 -0400
commit1e290deb5f670f8a65ee20fe8e095fe5786d1237 (patch)
tree1fe39cdc94f5160554031d69fd4f616508bfc4bb /commentary/stability.md
parent75e96c9edd4395e1554922cbb4de78c764b0d73f (diff)
Links to the TopAnswers language changes page
Diffstat (limited to 'commentary/stability.md')
-rw-r--r--commentary/stability.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/commentary/stability.md b/commentary/stability.md
index daccc1e5..8d433370 100644
--- a/commentary/stability.md
+++ b/commentary/stability.md
@@ -2,7 +2,7 @@
# Is BQN stable?
-The short answer is that code running online or in CBQN is unlikely to break. In rare cases we add experimental system values (the `•` things) before we're ready to commit to a particular design; read further or check on the forums if you'd like to know the status of a particular system function.
+The short answer is that code running online or in CBQN is unlikely to break. In rare cases we add experimental system values (the `•` things) before we're ready to commit to a particular design; read further or check on the forums if you'd like to know the status of a particular system function. And we are still making some backwards-compatible additions of moderate importance to core BQN: see [this page](https://topanswers.xyz/apl?q=1888). So it's possible that that extra knowledge will be needed to keep up with BQN in the future, but only a small amount.
I have thousands of lines of running BQN code including the self-hosted sources, website generator, and Singeli compiler. There are also now many BQN examples and REPL links [spread](../community/README.md) across the web which would be harder to change. So there is a strong reason to maintain compatibility for common or even moderately used features. Because BQN's been designed in a conservative way, avoiding fiddly decisions by keeping things simple, it seems that few compatibility breaks will be required. The history so far seems to bear this out.