Ideas for Porting PBP to Go

2026-05-24

May 24, 2026

I’ve written the PBP kernel in a pseudo-language and generate Python, JS and CL. I think that if you were to point your LLM at

and gave it the Python versions

it might be able to infer the Go version.

Maybe you also need to give it the Ohm grammar file

https://github.com/guitarvydas/pbp-dev/blob/main/kernel/emit.ohm

and the Python rewrite rules

https://github.com/guitarvydas/pbp-dev/blob/main/kernel/emitPython.rwr

I suspect that using words like “concurrent” and “process” and “thread” might get an LLM to generate convoluted / wrong code. 0D.rt implements its own form of multi-processing from scratch - don’t let an LLM use preconceived ideas about what threads are. Threading needs only 10’s of lines of code - all existing thread libraries that I know of (including Go) have turned this into a behemoth, steaming pile of complexity.

If you do need to use words like these, tell the LLM to use a mutual multi-tasking model (aka “green threads”) with NO shared memory. A lot of the cancerous complexity growth has befallen us because of the use of implicit memory sharing (starting with the concept of “thread safety”). When you strip the underlying memory sharing assumption out, the code becomes orders of magnitude simpler. The first kernel I studied was 1/2 page of assembler code.

Programming Simplicity

Discussion about this post

Ready for more?

Programming Simplicity

Ideas for Porting PBP to Go

2026-05-24

See Also

Discussion about this post

Ready for more?