261–269 of 269 posts
Earlier quoted context omitted.
Funny how HNers have such a high regard for his opinion on a domain he is well known for being sceptical and yet disregard his opinion, as UNIX co-author, that UNIX is well past its due date and is time to move on.
He's not a UNIX co-author at all, he joined Bell Labs in 1980.
Earlier quoted context omitted.
He's not a UNIX co-author at all, he joined Bell Labs in 1980.
Except he contributed to many of the userland tools and was part of the UNIX working group, which does make him a co-author, even if he didn't wrote the first kernel lines.
Earlier quoted context omitted.
Except he contributed to many of the userland tools and was part of the UNIX working group, which does make him a co-author, even if he didn't wrote the first kernel lines.
I must admit you have a strange definition of "co-author".
Earlier quoted context omitted.
I must admit you have a strange definition of "co-author".
I must admit you have a strange way to ignore Pike's contributions to UNIX initial GUI architecture, his book together with Kernighan about the UNIX programming environment and other contributions.
edit: Really? Downvotes? Not cool.
Earlier quoted context omitted.
I must admit you have a strange way to ignore Pike's contributions to UNIX initial GUI architecture, his book together with Kernighan about the UNIX programming environment and other contributions.
Please don't twist my words. I'm just saying "co-author" have different meanings for you and me. edit: Really? Downvotes? Not cool.
As for co-author, the Cambridge dictionary says:
"To write a book, article, report, etc. together with another person or other people:"
Which given Pike's participation on what defined the initial UNIX graphics userland, makes him a co-author.
Earlier quoted context omitted.
Please don't twist my words. I'm just saying "co-author" have different meanings for you and me. edit: Really? Downvotes? Not cool.
I didn't downvote you. As for co-author, the Cambridge dictionary says: "To write a book, article, report, etc. together with another person or other people:" Which given Pike's participation on what defined the initial UNIX graphics userland, makes him a co-author.
Earlier quoted context omitted.
Interesting. This seems very non-unix-y to me. The `tape_robot` doesn't "do one thing", it does many things, including parsing protobuf from shell strings and files, which seems error prone and way outside its core competency.
Maybe I misunderstood @jalfresi's idea - as I understood it, it was that each command would do not only parse protobuf and unix style flags, but also contain a RPC server of some sort. My reinterpretation was to say how about factoring out the server part, and leave the command only understanding either flags or protobuf commands - which could be delivered to the command either as an arg, or as a file given to it by…
The Unix Hater's Handbook ( https://en.wikipedia.org/wiki/The_Unix-Haters_Handbook ) has a few sections on of some of the ills of the Unix philosophy.
The UNIX Haters Handbook shows its age, it's criticizing a system that has only a passing similarity with modern unixes. But yes, it's funny.