2 ms·
Same, I think the file 'abstraction' is only valid for data flow. But whenever you have system components represented as files, you end up with a bunch of side
by agumonkey 8y ago
Same, I think the file 'abstraction' is only valid for data flow. But whenever you have system components represented as files, you end up with a bunch of side API bolted (kinda like ioctl in linux).
Plan 9 had a different view IIRC, something like everything has a protocol.
- pjmlp 8y agoYes, but Carmack had some issues having a framebuffer as file. https://marc.info/?a=111558719100068&r=1&w=4 https://marc.info/?a=111558719100068&r=1&w=4
- theoh 8y agoPlan 9's rio window system expected most graphical clients to use the draw functions, which operate by writing to /dev/draw. /dev/draw wasn't even a framebuffer—it was a control file that you wrote messages into. It clearly wouldn't have met Carmack's requirements though as the thread you link to points out, the Plan 9 team would have been happy for him to map the framebuffer into the address space of his process.
- agumonkey 8y agothis carmack guy is really not cut for graphics programming