Simple, expressive & portable programming language for efficient scripting
-
Updated
Nov 16, 2026 - Nim
Simple, expressive & portable programming language for efficient scripting
A minimalist, general-purpose programming language based on meta-programming and parse tree rewrites
Library for embedding a Rebol interpreter into C codebases
Fairly readable homoiconic language with primarily value (non-referential) semantics that balances the programmer's productivity with scalability
A Domain Representation Language
a new evolutionary highlevel and readable tape language (unlike brainf)
The Fundot programming language.
Symta is a list-processing Lisp dialect inspired by REFAL, POP-11, and MIT PLANNER, designed for extreme conciseness. It bundles forward/backward pattern matching, macros, classic OOP and ECS, and a C FFI in one tight syntax. A self-hosted compiler emits AOT bytecode for a small generational-GC runtime on Windows, macOS, and Linux.
Declarative data transformations as data
homoiconic scripting language
Homoiconic C - a universal data format for computation
Brain4it is an open source platform to develop artificial intelligence applications for the Internet of things.
Extensible and embeddable Psylla language implementation written in Java
Valentin Turchin's four-layer Refal supersystem, in Rust: a self-hosting Refal-5 compiler that drives (supercompilation over a graph of states), a reflection engine and a meta-prover. Metacomputation, term rewriting, partial evaluation, all three Futamura projections -- each measured against Turchin's own papers.
Homoiconic postfix concatenative programming language
Dialectic Programming Language for the Industrial Workstations of the World (the pun, not the semantics): a unityped, homoiconic, reflexive language with no typechecker, where a Judgement Evidence Graph records what is believed about each term and why. Pre-alpha; Chapel bootstrap.
🟥 Extremely minimalistic Io-like language
simple, homoiconic, two-dimensional, programming language
Ten analytic theory papers (Gregor, 2006, Type I) tracing the structural consequences of Puppet-Oriented Programming — of treating the program as a score performed and journaled by a Puppet rather than as instructions executed directly. Each paper names one structural property of software systems and traces its consequences.
To associate your repository with the homoiconic topic, visit your repo's landing page and select "manage topics."