i am on day 2 of implementing a fork of #golang called #moxie. so far i have managed to corral claude into successfully building almost every feature that is simple to do in Go without CGO, there is the actual immutable constant memory flag that will be in the full compiler, and the ability to embed dynamic libraries in the binary and load them and use their API via the C<->moxie function signature and basic types mappings.
so, i can now actually write code in moxie, theoretically. but there's a few more steps to go before i'm finished with this first stage bootstrap transpiler:
7. tooling - compile/link/lint/language server etc
8. optimization - adding compile time evaluation where possible, inlining hints to unwrap loops, SIMD where appropriate (hex already is, sha256 will be) profile guided optimization is an automation system that does multiple builds and analyses how the profile runs to increase optimization depth where the payoff is highest.
9. documentation - decent and comprehensive documentation, mostly it is about the transpiler itself and the language, and adapting existing go documentation with the feature changes (mostly removal and unifying things)
after that, i'm done, i can build moxie, and other people can figure it out too.
but i mean to get to the final stage of a fully self hosted compiler, so next step is rewriting moxie in moxie, and compiling that with the transpiler, then the first bootstrap is achieved. after that, then it moves to the code generator and implementing the low level functions because i'll be replicating and modifying the compiler and linker stages.
mleku
npub1fj…mleku
2025-11-10 09:56:36 UTC
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2025-11-10 09:56:36 UTCEvent JSON
{
"id": "39fdeba2c762dff12b442339366ca10c3275e96424fa3be88efc706928f96c19",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1762768596,
"kind": 1,
"tags": [
[
"t",
"golang"
],
[
"t",
"moxie"
],
[
"-"
]
],
"content": "i am on day 2 of implementing a fork of #golang called #moxie. so far i have managed to corral claude into successfully building almost every feature that is simple to do in Go without CGO, there is the actual immutable constant memory flag that will be in the full compiler, and the ability to embed dynamic libraries in the binary and load them and use their API via the C\u003c-\u003emoxie function signature and basic types mappings.\n\nso, i can now actually write code in moxie, theoretically. but there's a few more steps to go before i'm finished with this first stage bootstrap transpiler:\n\n7. tooling - compile/link/lint/language server etc\n\n8. optimization - adding compile time evaluation where possible, inlining hints to unwrap loops, SIMD where appropriate (hex already is, sha256 will be) profile guided optimization is an automation system that does multiple builds and analyses how the profile runs to increase optimization depth where the payoff is highest.\n\n9. documentation - decent and comprehensive documentation, mostly it is about the transpiler itself and the language, and adapting existing go documentation with the feature changes (mostly removal and unifying things)\n\nafter that, i'm done, i can build moxie, and other people can figure it out too.\n\nbut i mean to get to the final stage of a fully self hosted compiler, so next step is rewriting moxie in moxie, and compiling that with the transpiler, then the first bootstrap is achieved. after that, then it moves to the code generator and implementing the low level functions because i'll be replicating and modifying the compiler and linker stages.",
"sig": "4a6ae60a3ab07c9b98be64cd4b78a1a36ccbe3d8b67632db16b29ce9e090caed3df233a52c9f487531cb44a86e320510eb47a68a1a8603890b67f9b7bd856321"
}