From: Steve Nickolas <usotsuki@buric.co>
To: Andy Kosela <akosela@andykosela.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] more about Brian...
Date: Fri, 4 Feb 2022 03:10:16 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2202040304380.28373@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CALMnNGjfvtd=6qsmT6kXm3eEBM7OhhGSJ4Wbbjiv+B9P9rLafA@mail.gmail.com>
On Fri, 4 Feb 2022, Andy Kosela wrote:
> I used to be a big proponent of Go back in 2010. The language
> definitely felt fresh and minimal back then when Java and C++ were
> dominant on the market. And it definitely felt like the authors of Go
> wanted to replace them . It made sense in the Google environment, but
> very soon people realized that you can't write everything in Go.
> Garbage collector is cool but actually it prevents you from writing
> kernel or performance critical code, e.g. games.
>
> But Go became popular anyway. A lot of substandard PHP and New Age
> programmers started using it and it showed. In the beginning the
> humble authors of Go preferred minimal variable names and less than 80
> char lines. In time all this turned into Java-like long, expressive
> variable names and extremely long lines. I really hate lines longer
> than 80 chars...in any language. They are really hard to focus as you
> need to constantly move your eyes from left to right. The same
> phenomenon happens with very wide browser windows.
I tend to prefer to keep everything to 77-79 when I'm actually formatting
code for releases as opposed to "just don't care".
> And due to popular demand they started to add on to the language
> features: modules, generics, etc.. The language still feels a lot
> less bloated than C++, but IMHO plain old C just feels more natural
> and minimal.
I tend to feel that C strikes a perfect balance between minimalist and
powerful.
> And because I still program on a lot of old retro systems today I
> returned back to C. You can use C on pretty much everything -- from
> 8-bit machines to amd64. You can't say the same about Go.
Same.
I mean, I've started to pick up 8086 assembler, but I can write C, I can
code for my Apple //e, or I can code for my AMD64 boxen, or for my old
PS/2, or theoretically for my ancient Macintoshes...or a number of other
systems. It's not quite "write once run everywhere", but it's pretty
close.
-uso.
next prev parent reply other threads:[~2022-02-04 8:20 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 [this message]
2022-02-04 8:44 ` markus schnalke
2022-02-04 9:16 ` Steve Nickolas
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.2202040304380.28373@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=akosela@andykosela.com \
--cc=tuhs@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).