From: Steve Nickolas <usotsuki@buric.co>
To: markus schnalke <meillo@marmaro.de>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] more about Brian...
Date: Fri, 4 Feb 2022 04:16:02 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2202040413500.29844@sd-119843.dedibox.fr> (raw)
In-Reply-To: <1nFuCs-2RI-00@marmaro.de>
On Fri, 4 Feb 2022, markus schnalke wrote:
> You have to consider that each language is a child of its time;
> the culture of each programming language is shaped by the people
> who use it, write libraries and books and teach others.
>
> If you would introduce the C language today for the first
> time, it wouldn't become the same language that we like. Its
> libraries and culture would be very different because today's
> programmers are different. Likewise, would Go have been
> introduced in older times, it probably would have evolved
> differently.
Probably true.
> Thus, with liking the minimalist/powerful balance of C and the
> style of how programs in C are written (because that C culture
> has grown decades ago and is now also a part of the language)
> you actually say that you like the old times better than the new
> times. (I don't blame you for that.)
Could be that I cut my teeth on an 8-bit computer and did a lot of work on
16-bit systems, so I'm used to working with limited RAM and CPU.
> This all is much more about culture and what types of people
> program and the reasons why they program and the kinds of
> projects they do and the kinds of companies and their motivation
> in programming and how all this shapes the culture of any
> language ... than it is about specific languages itself, IMO.
There is certainly truth to that. And even human languages tend to adapt
in culture-specific ways ("two countries divided by a common language"
being a common joke about the US versus the UK, for example).
-uso.
next prev parent reply other threads:[~2022-02-04 9:16 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:46 [TUHS] ratfor vibe Will Senn
2022-02-01 15:37 ` arnold
2022-02-01 15:52 ` Ralph Corderoy
2022-02-01 16:58 ` Clem Cole
2022-02-01 17:02 ` silas poulson
2022-02-02 7:47 ` arnold
2022-02-03 5:47 ` [TUHS] more about Brian Rich Morin
2022-02-03 7:44 ` markus schnalke
2022-02-03 8:18 ` Rich Morin
2022-02-04 2:23 ` Adam Thornton
2022-02-04 2:34 ` [TUHS] more about Brian... [really Rust] Jon Steinhart
2022-02-04 13:07 ` Thomas Paulsen
2022-02-04 23:18 ` Dan Cross
2022-02-04 3:28 ` [TUHS] more about Brian Dan Stromberg
2022-02-04 5:11 ` Rich Morin
2022-02-04 21:22 ` [TUHS] Go vs. Rust, and etc. (was: more about Brian...) Greg A. Woods
2022-02-04 21:37 ` Richard Salz
2022-02-04 22:32 ` Steffen Nurpmeso
2022-02-04 23:05 ` Thomas Paulsen
2022-02-04 23:15 ` Seth J. Morabito
2022-02-05 1:41 ` Adam Thornton
2022-02-04 7:38 ` [TUHS] more about Brian Andy Kosela
2022-02-04 8:10 ` Steve Nickolas
2022-02-04 8:44 ` markus schnalke
2022-02-04 9:16 ` Steve Nickolas [this message]
2022-02-04 18:54 ` John Cowan
2022-02-04 19:45 ` Thomas Paulsen
2022-02-04 20:28 ` Hellwig Geisse
2022-02-04 21:03 ` Jim Capp
2022-02-04 22:30 ` Steffen Nurpmeso
2022-02-04 22:25 ` Steffen Nurpmeso
2022-02-06 0:56 ` Larry McVoy
2022-02-06 1:10 ` Will Senn
2022-02-06 4:52 ` Rob Pike
2022-02-06 4:58 ` Dan Halbert
2022-02-06 5:06 ` Will Senn
2022-02-06 6:19 ` Ed Carp
2022-02-06 6:27 ` Rob Pike
2022-02-06 6:40 ` Stuart Remphrey
2022-02-06 6:44 ` Bakul Shah
2022-02-06 19:08 ` Steffen Nurpmeso
2022-02-06 12:52 ` Ralph Corderoy
2022-02-06 13:14 ` Ed Carp
2022-02-06 14:13 ` Dan Cross
2022-02-06 14:15 ` Larry McVoy
2022-02-06 16:31 ` Warner Losh
2022-02-06 18:36 ` [TUHS] more about Brian... [ really GC vs malloc/free languages ] Jon Steinhart
2022-02-06 19:27 ` Jon Steinhart
2022-02-06 19:33 ` Warner Losh
2022-02-06 19:37 ` Jon Steinhart
2022-02-06 20:21 ` [TUHS] COFF is over there Ralph Corderoy
2022-02-06 16:16 ` [TUHS] more about Brian Brad Spencer
2022-02-08 5:22 ` Ed Carp
2022-02-03 18:57 ` [TUHS] ratfor vibe silas poulson
2022-02-04 8:26 ` arnold
2022-02-04 19:41 ` John Cowan
2022-02-10 15:18 ` Ralph Corderoy
2022-02-03 4:00 ` Will Senn
2022-02-03 4:31 ` Al Kossow
2022-02-03 5:16 ` Warner Losh
2022-02-03 20:00 ` Adam Thornton
2022-02-04 6:06 ` Ori Idan
2022-02-04 17:35 ` Adam Thornton
2022-02-04 17:44 ` Will Senn
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2202040413500.29844@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=meillo@marmaro.de \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).