12-29-2013, 06:50 PM
I have a better proposition. Instead of building a standard IS that all CPUs implement, have a solid IS that is then easily translated into each independent IS, possibly even in redstone hardware. (You'd run the program through a translator before running it, or translate it with a real computer program.) Compatible IS-es will require certain features of course, and it may not be optimized depending on the site-IS, but it's a better start.
On a side note,
<reserved for pipe architecture specifications>
On a side note,
<reserved for pipe architecture specifications>