Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Dan Cross <>
To: KenUnix <>
Cc: segaloco <>, COFF <>
Subject: [COFF] Re: [TUHS] Re: Generational development [was Re: Re: Early GUI on Linux]
Date: Mon, 27 Feb 2023 17:17:11 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Feb 27, 2023 at 5:06 PM KenUnix <> wrote:
> Have they not heard of common sense? Whenever I get something from git I look through it to
> check for something suspicious before using it and then and only then do I do make install.

Up to what size? What about the dependencies? How about the compiler
that compiles it all?

I have a copy of the Linux kernel I checked out on my machine; it's
many millions of lines of code; sorry, I haven't read all of that. I
often install things using the operating system's package manager; I
haven't read through all that code, either. Life's too short as it is!

> And today's cookie cutter approach to writing software means they are not learning anything
> but copy paste. Where's the innovation?

I imagine that when people made the switch from programming in machine
code to symbolic assemblers, and then again from assembler to
higher-level languages (FORTRAN! COBOL! PL/I!). And so on.

Consider that, perhaps, the innovation is in how those things are all
combined to do something useful for users. My ability to search, read
documents, listen to music, watch real-time video, etc, is way beyond
anything I could do on the machines of the early 90s.

Not everything that the kids do these days is for the better, but not
everything is terrible, either. This list, and TUHS, bluntly, too
often makes the mistake of assuming that it is. Innovation didn't stop
in 1989.

        - Dan C.

> On Mon, Feb 27, 2023 at 4:22 PM Dan Cross <> wrote:
>> [COFF]
>> On Mon, Feb 27, 2023 at 4:16 PM Chet Ramey <> wrote:
>> > On 2/27/23 4:01 PM, segaloco wrote:
>> > > The official Rust book lists a blind script grab from a website piped into a shell as their "official" install mechanism.
>> >
>> > Well, I suppose if it's from a trustworthy source...
>> >
>> > (Sorry, my eyes rolled so hard they're bouncing on the floor right now.)
>> I find this a little odd. If I go back to O'Reilly books from the
>> early 90s, there was advice to do all sorts of suspect things in them,
>> such as fetching random bits of pieces from random FTP servers (or
>> even using email fetch tarballs [!!]). Or downloading shell archives
>> from USENET.
>> And of course you _can_ download the script and read through it if you want.
>> And no one forces anyone to use `rustup`. Most vendors ship some
>> version of Rust through their package management system these days.
>>         - Dan C.
> --
> End of line

  parent reply	other threads:[~2023-02-27 22:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
2023-02-27 21:22       ` Dan Cross
2023-02-27 21:42         ` Chet Ramey
2023-02-27 22:01           ` Dan Cross
2023-02-27 23:23             ` Chet Ramey
2023-02-27 23:42               ` Larry McVoy
2023-02-28  0:29                 ` Dan Cross
2023-02-28  0:28               ` Dan Cross
2023-02-28 14:53                 ` Chet Ramey
2023-02-28 15:25                   ` Dan Cross
2023-02-28 16:03                     ` Chet Ramey
     [not found]         ` <>
2023-02-27 22:07           ` [COFF] Re: [TUHS] " Dan Cross
     [not found]         ` <>
2023-02-27 22:17           ` Dan Cross [this message]
2023-02-27 23:20             ` [COFF] Re: [TUHS] " Stuff Received
     [not found] <>
     [not found] ` <Y/>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
2023-02-27 21:04             ` Dan Cross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).