3 ms·
> we just put 16MB of working memory on each chip. Just? The chips we've got have between 32kb and 64kb -- maybe 128kb in some really big chips, and it's been
by geocar 4y ago
> we just put 16MB of working memory on each chip.
Just? The chips we've got have between 32kb and 64kb -- maybe 128kb in some really big chips, and it's been that way for forty years! Everything else has to swap or cache through messaging layers (L2, L3) with real latency because we can't "just" put a bunch of memory on a chip.
I mean, I like thinking about star-trek computers too, but "just" isn't the word I would use for something like this... What would you possibly do with so much memory in a circuit?
> But what do you do with all of the existing C code? I think for backward compatibility you'd need to implement virtual memory at the working memory layer.
People rewrote almost everything in Java. And are doing it again with Rust. Programmers want to program, and if they can't come up with anything else to do, they'll just rewrite what someone else did. I don't think you should valuate existing C code the way its owners do, but by how their competition will valuate it; If someone can use FutureLang to outperform their business-competition who uses C, this problem will solve itself.