Imagine haranguing someone on the internet for work they did nearly 30 years ago, and having the audacity to insist they change it.
Is simply reporting errors considered “haranguing” and “having the audacity to insist they change it”? Do you have the same attitude towards people who report bugs in your code?
it varies; sometimes people are being helpful by reporting bugs, for example because they don't know how to fix the bugs themselves, or because they're paying me to solve their problems so knowing what those problems are is the first step in getting paid, but sometimes they're just griefers looking for someone to bully
i suggest you fix the errors in your copy of the page and post the url here
>Putting things together from a kit of parts isn't necessarily the optimal way to do many things. In many cases tight integration actually produces superior results, and debugging a system made from many cooperating bits isn't necessarily any easier. The reason why this is part of the Unix philosophy is not merely because of the productivity it provides, but largely because of the power it affords end users. Most of…
I think back to my days teaching at a college whose CS labs ran on NetWare 3. For “reasons” the user accounts were things like PASCAL; all the students in a course that used Pascal used this account (and kept their files on floppies). I wanted to move to an environment where students had individual accounts. The IT folks said that was way too much work to implement, and showed me the GUI (or TUI?) app they used to ma…
So absolutely true. I work in an “operational facing” engineering group. We are engineering but process data (daily/monthly data processing for factory and customer requests).
Having a composable process using the Unix philosophy makes it trivial to stop processing at any point in the work flow for that one customer request that comes up once a year. There is no ROI to make the work flow support these edge cases, it’s cheaper even after a decade or more just to one-off these special cases.
But this would be completely impossible if we didn’t architect the system in smaller components. As you say, it’s not text processing, it is units of processing that can be composed, stopped, reordered or have a custom step in the middle.