urbit/developers.urbit.org
1
1
Fork 0
mirror of https://github.com/urbit/developers.urbit.org.git synced 2024-09-11 13:55:59 +03:00
Code Issues Packages Projects Releases Wiki Activity

Put figure caption below figure.

Browse Source
This commit is contained in:
Sigilante 2023-01-09 12:22:12 -06:00 committed by GitHub
parent 8fa506c34e
commit e3520b91db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/blog/rune-frequency-202212.md
View File

@ -169,10 +169,10 @@ This technique converted irregular syntax to regular syntax, but did not desugar
Rune frequency follows a [power-law distribution](https://en.wikipedia.org/wiki/Power_law) with 18 runes representing 80% of total rune utilization. Indeed, several runes are _hapax legomena_ in `/sys` ([`|?` barwut](https://developers.urbit.org/reference/hoon/rune/bar#-barwut), [`~<`](https://developers.urbit.org/reference/hoon/rune/sig#-siggal)) or do not occur at all (discussed below).
**Figure 1**. Observed rune frequency in `/sys` as a power law.
![**Figure 1**. Observed rune frequency in `/sys` as a power law.](https://storage.googleapis.com/media.urbit.org/blog/rune-frequency.png)
**Figure 1**. Observed rune frequency in `/sys` as a power law.
(Bear with me on that graph: it's rather hard to display order runes in any sort of coherent way I've come up with so far.)