News for hackers. Stuff that matters.
Re:Non-Posix File Systems by ridiculous_fish on Tuesday September 08, 2020 @07:51PM (#24415001)
How did Plan 9 allow its APIs to evolve? For example, reading /dev/mouse returns records that are exactly 49 bytes, in text format [1]; how did they add new fields without breaking every app?

1: http://man.cat-v.org/plan_9/3/mouse

Re:Non-Posix File Systems by eadmund on Wednesday September 09, 2020 @08:15AM (#24420164)
As a sibling notes, they could have just added a new file while supporting the old format, but they had some leeway in the format itself: the buttons value only uses three bits.

Had they been a little more clever and used a delimited format like S-expressions, they could have simply specified that each mouse event would generate one S-expression, and clients could have read one expression at a time.

Re:Non-Posix File Systems by sedatk on Tuesday September 08, 2020 @08:07PM (#24415148)
They’d probably have /dev/mouse and /dev/mouse2 simultaneously.
Re:Non-Posix File Systems by saagarjha on Wednesday September 09, 2020 @06:14AM (#24419400)
I guess you could call it a stricter version of the Linux’s kernel’s ABI stability?
Re:Non-Posix File Systems by anthk on Tuesday September 08, 2020 @10:51PM (#24416429)
namespace