permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 1f973177313d792be7f9e6ee4d5ec17b48925fc2
parent e4a42dc7384f6a73f89dbcf5f2e7bb3876ce7526
Author: neau <neau@web>
Date:   Wed, 22 Jun 2022 00:23:36 +0200

empty web commit

Diffstat:
Mbedrock_platform.mdwn | 8++------
1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/bedrock_platform.mdwn b/bedrock_platform.mdwn @@ -1,8 +1,8 @@ -A **bedrock platform** is a [[hardware]] platform or a simple [[virtual machine]] that can be expected to remain compatible with any [[software]] that has ever been written for it. Bedrock platforms can be used to prevent [[software rot]]. +A **bedrock platform** is a [[hardware]] platform or a universal [[virtual machine]] that can be expected to remain compatible with any [[software]] that has ever been written for it. Bedrock platforms can be used to prevent [[software rot]]. Some possible criteria for bedrock hardware: -* The hardware has been popular and commonly available at some point of history (and preferrably remains that way). +* The hardware has been popular and commonly available at some point of history (and preferably remains that way). * Every detail of the hardware is well-known and fully documented. (Having a 100% compatible open-source emulator can be considered full documentation) * There have been several independent manufacturers for each component. * Multiple emulators for the platform are commonly available for many different environments. @@ -20,10 +20,6 @@ Candidates for bedrock hardware: For virtual bedrock hardware, the main criterion is that the specification is simple enough that it can be implemented in a small effort for commonly available computers, and that the specification is unambiguous and frozen. -Candidates for virtual machine bedrocks: - -* [[Uxn]] - Even though optimal resource use is not a major point in bedrock platforms, having that as well would be ideal. Not only should it be possible to make minimal-overhead emulators, but to read, [[analyze|static code analysis]], [[decompile|decompilation]] and recompile the code in order to use it on arbitrary future computers. Writers of bedrock-platform software may want to make sure that it will be easy enough to e.g. separate code from data even when analyzing binaries. See also: