Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: John Ames Newsgroups: comp.os.linux.advocacy,comp.os.linux.misc Subject: Re: What Thinkest Thou Of LO Donate Banner? Date: Fri, 21 Nov 2025 14:33:33 -0800 Organization: A noiseless patient Spider Lines: 27 Message-ID: <20251121143333.00001168@gmail.com> References: <1864d8e7ae136b94$115$2498948$802601b3@news.usenetexpress.com> <10a4ph3$obcm$2@dont-email.me> <68c5ef9f@news.ausics.net> <10a5sou$1360o$7@dont-email.me> <10fcb5j$3enl$1@dont-email.me> <20251120145948.00000987@gmail.com> <10fo9nn$3a6ib$3@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Date: Fri, 21 Nov 2025 22:33:57 +0000 (UTC) Injection-Info: dont-email.me; posting-host="aadc20a9039a902119dee5fc438f8de5"; logging-data="3604"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+nHVSb7xaABUa+ZGMenR0Qa8vl1XgR0x4=" Cancel-Lock: sha1:AX+2t/XaNEvPHwr+xL0WfLyRHgQ= X-Newsreader: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Xref: csiph.com comp.os.linux.advocacy:701479 comp.os.linux.misc:77789 On Thu, 20 Nov 2025 23:54:31 -0000 (UTC) Lawrence D=E2=80=99Oliveiro wrote: > Microsoft spent decades conditioning its user base to be allergic to > the command line. Then it suddenly did an about-face and now tries to > claim that the command line is cool again. >=20 > I guess the Windows user base alternates between fear, suspicion and > incredulity, while the *nix world looks on in amusement ... The NT power-user set have always been comfortable with the command line; the main problem was that for many a year the WinNT CLI (cmd.exe) was only a moderate improvement on the old DOS/Win9x command.com - which offered little more than basic wildcard expansion and control flow, and didn't really do anything other than move files around and launch programs with programmatically-specific arguments. Functional, technically, but not pretty, and extremely limited in its ability to interact with the Win32 environment. PowerShell, on paper, offers a whole huge chunk of functionality that cmd.exe never did, with hooks for practically everything available to scripts directly. The problem is that actually finding out what those hooks *are* (and which esoteric namespace you have to import to use them) inevitably involves slogging through an endless morass of SpiceWorks threads and/or digging up the fossilized remains of long- extinct MSDN pages on archive.org :/