pua-lang: A Rust Monkey Dialect That Renames Syntax to Mock Alibaba Management Speak

What pua-lang actually is and who it targets

pua-lang is a fork of rs-monkey-lang, which itself is an implementation of the Monkey language from the book Writing An Interpreter In Go. The project's stated purpose is to mirror the 'inspirational babble' of Alibaba managers, using the acronym PUA to reference manipulative workplace tactics. The audience is twofold: programmers learning how interpreters work, and people who find corporate jargon funny. If you do not care about Monkey or do not appreciate the satire, this project offers little beyond a renamed syntax tree.

The keyword renaming is the entire point

The core mechanism is a lexical substitution table. Every Monkey keyword maps to a Chinese phrase: if becomes 细分, else becomes 路径, while becomes 闭环, true becomes 三七五, false becomes 三二五, let becomes 赋能, fn becomes 抓手, return becomes 反哺, and puts becomes 输出. Operators are renamed too: + is 联动, - is 差异, / is 倾斜, and = is 对齐. The README explicitly says the precise set of renames may change, and directs you to read src/lexer/mod.rs and src/evaluator/builtins.rs to understand the current mappings. This means the language is not stable; you cannot rely on a keyword staying the same across versions.

Syntax and semantics: mostly Monkey with a few twists

The grammar follows Monkey closely. You get variable bindings, integers, booleans, strings, arrays, hashes, functions, closures, and higher-order functions. The README shows a Fibonacci function written in pua-lang, which looks like a normal C-like language once you translate the keywords. One notable addition is Unicode identifiers, which follow UAX #31 (XID) plus monetary extensions like ¥, $, and an 'overly-lax' definition of emojis. This means you can name variables with emoji, as shown in the example 赋能 不变 = 抓手(工资p6) { ... } where the parameter is 工资p6 and the string includes emoji. The language does not support floating-point numbers; only integers are allowed, matching Monkey's design.

Building and running: REPL and WASM playground

The README gives two ways to run pua-lang. First, clone the repository and run make repl, which presumably builds the Rust interpreter and starts a REPL. Second, there is a WASM playground hosted at https://flaneur2020.github.io/pua-lang/. The README admits the output streams do not work properly in the playground because Rust has no I/O redirection and wasm32-unknown-unknown has no I/O by default. That is a concrete limitation: if you try the playground, do not expect stdout to appear as you might in a terminal. The REPL is the reliable path, assuming your Rust toolchain is set up.

Where pua-lang falls short: incomplete features and broken I/O

The documentation lists several gaps. The 细分 (if) construct supports a general form, and 路径 (else) exists, but the combined '细分 路径' (else if) does not exist yet. That means you cannot chain else-if conditions, which is a real restriction for writing non-trivial logic. Also, floating-point numbers cannot be handled, so any numeric code requiring decimals fails. The WASM playground's output streams are broken, which the README acknowledges. These are not hypothetical issues; they are stated limitations. If you need else-if chains or floats, pua-lang is the wrong tool.

Alternatives: rs-monkey-lang and the original Monkey

The direct alternative is rs-monkey-lang, the upstream project that pua-lang forked. It implements the same Monkey language but with standard English keywords like if, let, and fn. If you want to learn interpreter construction without the satirical renaming, rs-monkey-lang is the more predictable choice. The original Monkey language from the book Writing An Interpreter In Go is another alternative, with a reference implementation in Go. The difference is approach: pua-lang adds a lexical layer that maps Chinese phrases to tokens, while the alternatives keep the syntax as-is. If you want to study the interpreter mechanics, the upstream version is clearer because you do not have to translate keywords in your head.

Maintenance and licensing

The project is licensed under the MIT License, which permits commercial use, modification, and redistribution with attribution. The repository is not archived, and the last push date is unknown, which means you cannot assess how actively it is maintained. The README warns that the keyword set may change, so any code you write against pua-lang could break with a new commit. Since it is a fork, you also inherit the maintenance burden of tracking upstream changes in rs-monkey-lang if you want bug fixes. The documentation itself is marked with a warning that there may be mistakes, so treat the README as a guide, not a specification.

Editorial conclusion

Adopt pua-lang if you want a small, readable interpreter to study or extend, and if you appreciate satirical naming that mocks management culture. Do not use it for any production work: it lacks floats, has incomplete if-else chaining, and the WASM playground has broken I/O. Before adopting it, verify the exact keyword mappings in src/lexer/mod.rs and src/evaluator/builtins.rs, since the README warns the renames change over time. The project is a fork of rs-monkey-lang, so expect to track upstream changes if you rely on it.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. README
4. Releases