We are currently working on new rules for what content should and shouldn't be allowed on this website, and are looking for feedback! See Esolang:2026 topicality proposal to view and give feedback on the current draft.
Talk:Research on compiling Javascript to Brainfuck
An approach with intermediate stack machine looks viable (something like python bytecode). I.e. translate JS to stack machine first, then translate stack machine into BF. --Blashyrkh (talk) 10:34, 25 June 2026 (UTC)
And it's worth mentioning that since brainfuck lacks subroutines, you probably have to execute stack machine bytecode (encoded into brainfuck program as plain data) by brainfuck program instead of "compiling" stack machine bytecode into brainfuck. So, output brainfuck code looks like most BF quines: data section first (in your case it's the encoded stack machine bytecode) and then brainfuck runner (always the same). And the "compilation" process consists of two phases: compile JS (or anything else) to stack machine, and then simple translate stack machine bytecode into brainfuck. --Blashyrkh (talk) 10:47, 25 June 2026 (UTC)