A hierachy of languages including transpilers and using partial evaluation to create (in the end) self modifying executables
Self-hosted means that no part of the system relies on external dependencies, apart from the operating system kernel off course.
An object machine means that the whole system is defined in terms of objects. No C with or without plusses or parts of the C world. Just the system and the kernel. Object based would be a fitting word.
The previous failures led to a very partial ruby compiler that i will replace with a partial evaluator in the future.
But to write the evaluator i first need to write a static language (also kide), for which i can reuse part of the old code that has:
The architecture is a bit in flux, the blog is more up to date
I just finished writing a compiler for Som-st which was sucessful, but did move the needle more towards partial evaluation.
The next steps will be more on the foundation, building a crystal like static language and compiler as the basis for partial evaluation and interpretation.
The third goal, more a neccessity, is to rework the bootstrap mechanism. This may mean using more tools, but also less ruby magic. this will start with a design phase.
Apart from the high level Plans (above) there is still a lot of work, here are some of the next few topics
The Docs are organized a bit like a book, some of the main links are in the main menu, eg architecture menu.
This page, status, plans and upcoming are updated as the project progresses. New ideas and major milestones are in the news section. The docs sections are updated with the actual state of affairs.
To get to know the system, there is also an interpreter and a basic visual debugger.
Last but not least, I try to get recent developments down on paper when they are still fresh. Though not much has happened lately, as we bought this
Multi layered evaluation (2026-04-25)
