3 ms·
The way to close the gap is incompatible with the way we're all used to programming. Alternative computing architectures are required to get there. Imagine a R
by mikewarot 5y ago
The way to close the gap is incompatible with the way we're all used to programming. Alternative computing architectures are required to get there.
Imagine a RISC CPU with a chunk of Static RAM, running slow (100 Mhz), and synchronously, with no need for any of the usual tweaks like cache, pipelines, branch prediction, etc. Such a CPU would be very small, and if you sized the RAM correctly, you could put all of it into a grid that would more than make up for the slow clock rate, and still be fairly low power.
In the end, though, I think we'll end up programming arrays of 4x4 bit look up tables that talk to their neighbors. But not directly, through a few layers of optimizing compilers. The advantage is that it could be fast, fault tolerant, and would all run in parallel. You could compute as fast as you could shovel data in one end, and out the other.
- KeyXiote 5y agoIn terms of hardware a "new" substrate other than silicone will likely be in part a probable solution. The requirements for speed will be density on localization of components and how they communicate. Metal traces are suboptimal compared to a substrate base that could gate itself in relation to I/O. Having ionic neutral properties as well as the ability to take or give a charge functionally and on demand, would be dependant on a functional catalyst and the relational chemical structure of the substrate selected to build physical architecture on.