Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Muttley@dastardlyhq.com Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc Subject: Re: Python (was Re: I did not inhale) Date: Wed, 21 Aug 2024 07:36:58 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: References: <20240412094809.811@kylheku.com> <87il0mm94y.fsf@tudado.org> <87il0lldf8.fsf@tudado.org> <20240815182717.189@kylheku.com> Injection-Date: Wed, 21 Aug 2024 09:36:58 +0200 (CEST) Injection-Info: dont-email.me; posting-host="47a613f3f74a4b778efde26a501a57a1"; logging-data="3986345"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/XsLUt8PH5nkJk/UVzcdAA" Cancel-Lock: sha1:Rmz6RElxBHwsBfK/jVmnUIl9j5o= Bytes: 2558 On Wed, 21 Aug 2024 09:26:41 +0200 David Brown boringly babbled: >So I don't question that it is interesting, informative, or a pleasure >to read. I question that it is /necessary/. You simply cannot argue >that people who want to program for Linux /must/ read that book. There >is no justification for that claim. There is no justification for >claiming that people wanting to program for Linux need to read any books >on the topic at all, nor for claims that people need to "know POSIX" to >be able to write code for Linux and/or in C. Only knowing core C will severely limit what you can do on any OS. If you're happy just coding up file processors or some self contained mathematical algo and simply writing to stdout or a file then fine, but to do anything more sophisticated you'll need to know the OS API whether its posix + X on *nix or Win32 on Windows. >There are a thousand and one ways to learn about the workings of Linux - >and that's counting "reading books" as one way, regardless of /which/ Linear learning is usually better than snippets from google. If you want to learn a shakespear play you read the book, you don't google little bits of it at a time.