Eugene Leitl wrote:
> Mapping an algorithm into reecofigurable hardware is *faster* than
> doing it all-purpose hardware, unless you can have a silicon
> foundry within your computer which can churn out new dedicated
> ASICs at a MHz rate. With reconfigurable architectures, you swap
> out virtual circuitry, not code. In fact reconfigurable hardware
> allows the creation of very dynamic, hyperactive machines
> with unified data/code, the most efficient things theoretically
> possible. These things are very new, so even academia doesn't
> quite know how to tackle them yet. You certainly can't go Darwin
> in machina (the next thing after OOP) without them.
I came upon this paper a couple of years ago while looking over
it's pretty impressive.
-- mailto:firstname.lastname@example.org http://i.am/dwayne "the cricher we kno as dwayne is only the projection into our dimension of something much larger and wirder." ---email@example.com ....return....to....the....source....