3 ms·
That just moves the problem to that remote system. I think a better example are image-based systems such as Smalltalk, lisp, and Forth do not even need a file
by Someone 12y ago
That just moves the problem to that remote system.
I think a better example are image-based systems such as Smalltalk, lisp, and Forth do not even need a file system (traditional forth systems are the simplest here; they had one way to read in data: BLOCK (http://c2.com/cgi/wiki?ForthBlocks) http://c2.com/cgi/wiki?ForthBlocks))
And of course, the home computers of the '80s ran their (single) application (typically a Basic interpreter, but in the case of the http://en.wikipedia.org/wiki/Jupiter_Ace http://en.wikipedia.org/wiki/Jupiter_Ace, a Forth) from ROM.
- jacquesm 12y agoSo you get a ton of code that tries to shoehorn some subset of file operations and similarities into a block structure, effectively recreating a file system. A file is a 'series of blocks' after all (that's what your inode table does it, it remembers which files start where, and a series of indirections then access the actual data blocks). Operating systems abstract out all that common stuff, present a (somewhat) reasonable interface to it, handle multiple users if the system has those and then get out of the way as much as possible. Operating systems that try to do more invariably fail(ed) and operating systems that try to do less end up being great for embedded work but in general not much beyond that.