A detailed progress report on Aiki, an experimental programming language, covering work done since the first public alpha release. The author, tagging the current state as v0.4.0-alpha-26, describes moving grammar authority out of parser code, centralizing structural analysis, fixing tooling failure-propagation bugs, making the runtime location-independent, and building an independent Aiki-written lexer, parser, and evaluator that can self-host and even recursively interpret itself. Also covered: a new editor-independent language service layer used by Xed, VS Code, and nvi; a profiler calibration experiment validating semantic counters; and plans for future work on process execution, networking, JSON, OS surface, signals, timers, and cryptographic hashing.

20m read timeFrom decuser.github.io
Post cover image
Table of contents
Authority and the GrammarTooling and Failure SemanticsDistribution and Location IndependenceAn Independent Aiki Front EndLanguage ServicesFrom Parser to InterpreterModules and the HAL BoundaryBehavioral ConformanceRecursive Self-InterpretationProfiling the ProfilerExperiments Are Not TestsThe CommitmentsPlatformsPending WorkFuture DirectionAiki at v0.4.0-alpha-26Where This Leaves Aiki
147 Impressions