4 ms·
I don’t disagree with your general point, but for this specific assertion: > something on a flash drive the requires millions of lines of code to read data of
by derefr 8y ago
I don’t disagree with your general point, but for this specific assertion:
> something on a flash drive the requires millions of lines of code to read data of
Does it really require millions of lines? Even if you’re just targeting that one model of drive, rather than writing a general purpose SATA/USB kernel stack? If what’s on there is, say, JPEG images, libjpeg (plus its dependencies in glibc, I guess) isn’t “millions of lines” either. Where are these millions of lines?
(I’m speaking as someone who has written a unikernel with disk IO and graphics support. It was far less than a million lines!)
- ics 8y agoI think they're considering the entire start-to-finish process of viewing, i.e. mounting the drive, decoding the jpeg, displaying on screen.
- HarryHirsch 8y agoCompare the BBC Domesday Project to the original Domesday Book from 1085. One can be read today, the other not so much. You ask what the folks at BBC were thinking, did they never consult an archival librarian?
- jacquesm 8y agoI played with that when it first came out. We had the discs and the player, it was very impressive but even then I knew that there was no way that it would last for even a decade. It was a puny bit of data for todays standards (about 500M in total), but of the day it was incredible. Back then a mainframe winchester pack with the same capacity would be roughly the size of a washer-dryer combination. The data not being publicly accessible at the moment is more of a copyright rather than a technical issue.