3 ms·
Because then everything is not a file, it's either a stream-based file or a record-based file. So you don't have a uniform API for everything. The UNIX way wou
by rakoo 6y ago
Because then everything is not a file, it's either a stream-based file or a record-based file. So you don't have a uniform API for everything.
The UNIX way would be to have a filesystem that does all the internal logic of checking line width, and allow the user to mount it. One API, different functionality
- tyingq 6y agoWell, we re-invent it anyway on top of stream files, so I'm not sure I get the difference other than fragmentation of solutions.
- rakoo 6y agoBecause in the UNIX way you'd have one process for providing record-based files, one process to write to/read from them, one process to parse the query language into an AST, one process to maintain indexes, etc... and all of this would be bound by a big jar of glue-shell. It's much easier to just do everything inside a single software as a monolith than to distribute functionalities, I don't think one needs to look further than that