News for hackers. Stuff that matters.
Re:The Beauty of Unix Pipelines by remexre on Friday June 05, 2020 @03:21AM (#23425908)
Sure, I mean more like there'd be some interface ByteStream, and probably another interface TerminalInput extends ByteStream; TerminalInput would then contain the especially terminal-related signals (e.g. sigwinch). If a program doesn't declare that it wants a full TerminalInput for stdin, the sigwinches would be dropped. If it declares it wants one but the environment can't provide one (e.g. stdin is closed, stdin is a file, etc.) it would be an error from execve().

Other signals would be provided by other resources, ofc; e.g. sigint should probably be present in all programs.

---

In general, my ideal OS would have look something like [0], but with isolation between the objects (since they're now processes), provisions for state changes (so probably interfaces would look more like session types), and with a type system that supports algebraic data types.

[0]: https://www.tedinski.com/2018/02/20/an-oo-language-without-i...

Re:The Beauty of Unix Pipelines by Bystroushaak on Wednesday June 17, 2020 @08:19PM (#23558412)
I have written something on this topic previously: http://blog.rfox.eu/en/Programmers_critique_of_missing_struc...