aboutsummaryrefslogtreecommitdiff
path: root/docs/problems.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/problems.html')
-rw-r--r--docs/problems.html1
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/problems.html b/docs/problems.html
index 5f053696..b2ea1faa 100644
--- a/docs/problems.html
+++ b/docs/problems.html
@@ -1,4 +1,5 @@
<head><link href="style.css" rel="stylesheet"/></head>
+<div class="nav"><a href="https://github.com/mlochbaum/BQN">BQN</a></div>
<h1 id="problems-with-bqn">Problems with BQN</h1>
<p>Every language has some issues that everyone can agree make programming harder. Sometimes there is a simple solution that has not yet been discovered; sometimes the problem is inherent to the language because it's caused by fundamental choices (or anywhere in between). Below are problems I have identified in BQN, ordered from what I consider the most severe to the least. This is independent of whether the issue can be solved—if it somehow went away, how much better would the language be?</p>
<p>I've omitted problems that are obviously addressed by speculated extensions. Of course adding A fixes the problem &quot;doesn't have A&quot;. Problems that only exist in reference to some existing convention (e.g. unfamiliarity to APLers) are also left out, unless the convention manifests technically (Unicode support).</p>