This is the latest in a very honourable tradition. My first encounter with it was with Martin Richards's BCPL system in 1972. The compiler generated a hypothetical ISA called OCODE, from which backends generated pretty good native code for Titan-2 and System/360, among others. One of those backends generated INTCODE, which was an extremely reduced ISA, for which an interpreter could be easily written (I wrote one in…
Show HN: Bedrock – An 8-bit computing system for running programs anywhere
21–30 of 69 posts
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#22One of the big differences from Uxn is the introduction of undefined behavior; by design, you can break it, unlike Stanislav's legos. So presumably Bedrock programs, like C programs, will do different things on different implementations of the system. That's not fatal to portability, obviously, just extra write-once-debug-everywhere work.
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#23This is the latest in a very honourable tradition. My first encounter with it was with Martin Richards's BCPL system in 1972. The compiler generated a hypothetical ISA called OCODE, from which backends generated pretty good native code for Titan-2 and System/360, among others. One of those backends generated INTCODE, which was an extremely reduced ISA, for which an interpreter could be easily written (I wrote one in…
Wouldn't the 32-bit variant just be WebAssembly?
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#24Why 8 bit?
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#25Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#26Earlier quoted context omitted.
Wouldn't the 32-bit variant just be WebAssembly?
No, the WebAssembly spec is over 200 pages.
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#27For people curious about the differences between this and Uxn (as I was): https://benbridle.com/articles/bedrock-differences-from-uxn....
how does that work?
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#28I'm not steeped in computer science, so please pardon me if the following are dumb questions. > Programs written for Bedrock can run on any computer system, so long as a Bedrock emulator has been implemented for that system. Isn't that true of any program? As long as the language that the program is written in is implemented on the system, any (valid?) program in that language will run on that system?
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#29For people curious about the differences between this and Uxn (as I was): https://benbridle.com/articles/bedrock-differences-from-uxn....
> each pixel having both a foreground and a background colour how does that work?
Re: Show HN: Bedrock – An 8-bit computing system for running programs anywhere
#30I'm not steeped in computer science, so please pardon me if the following are dumb questions. > Programs written for Bedrock can run on any computer system, so long as a Bedrock emulator has been implemented for that system. Isn't that true of any program? As long as the language that the program is written in is implemented on the system, any (valid?) program in that language will run on that system?
In practice, this is not always so straightforward, especially as you move closer to machine-level details or consider compiled binaries.
Many compiled programs are built for a specific architecture (x86, ARM, etc.). They won’t run on a different architecture unless you provide either: A cross-compiler (to generate new native code for that architecture), or an emulator (which mimics the old architecture on the new one)