Deutsch English Français Italiano |
<va4fbr$3qvij$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: 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 10:26:03 -0000 (UTC) Organization: A noiseless patient Spider Lines: 23 Message-ID: <va4fbr$3qvij$1@dont-email.me> References: <uu54la$3su5b$6@dont-email.me> <uvbfii$3mom0$1@news.xmission.com> <20240412094809.811@kylheku.com> <87il0mm94y.fsf@tudado.org> <way-20240413091747@ram.dialup.fu-berlin.de> <87il0lldf8.fsf@tudado.org> <choices-20240413123957@ram.dialup.fu-berlin.de> <v9lm2k$12qhv$1@dont-email.me> <v9m4gd$14scu$1@dont-email.me> <20240815182717.189@kylheku.com> <v9npls$1fjus$1@dont-email.me> <v9t204$2dofg$1@dont-email.me> <va28pi$3dldm$1@dont-email.me> <va2ro9$3gd7v$1@dont-email.me> <va2vt0$3h3gj$1@dont-email.me> <va44rh$3p1l6$1@dont-email.me> <va45eq$3pkt9$1@dont-email.me> <va4aut$3q4g0$1@dont-email.me> Injection-Date: Wed, 21 Aug 2024 12:26:03 +0200 (CEST) Injection-Info: dont-email.me; posting-host="47a613f3f74a4b778efde26a501a57a1"; logging-data="4030035"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX193X4B90tcVIHdM4Af6Ktxe" Cancel-Lock: sha1:2bEwPiJCa8b7qnuN/b6tJaWmV7o= On Wed, 21 Aug 2024 11:10:53 +0200 David Brown <david.brown@hesbynett.no> boringly babbled: >If you are writing network software for Linux, how is it relevant to >learn about the sound API, or the more advanced filesystem API's ? If You don't, but the subsystems don't exist in isolation, there's a lot of overlap. Eg network sockets use a lot of the same API functions as files (eg: read, write, fcntl, ioctl) so understanding may well help to understand the other. >you are writing a gui program with QT, why should you be interested in X >APIs or POSIX threading and file handling - you'll be using the QT >libraries and APIs for graphics, threading and file handling. Not necessarily. >I have not suggested, or even hinted, that all you need is "core C" - >what you need is the knowledge that is relevant to the task at hand, >regardless of the OS, language, or whatever. Its certainly the impression you gave.