From: Andy Kosela <akosela@andykosela.com>
To: ron minnich <rminnich@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: yet another C discussion (YACD) and: Rust is not C++
Date: Mon, 30 Jan 2023 19:47:19 +0100 [thread overview]
Message-ID: <CALMnNGiXVeqBznYwhPmwR-jUtq2OMO64HHc2A4F0o+PFJMu3Fw@mail.gmail.com> (raw)
In-Reply-To: <CAP6exY+_YKkJ2vHpz2sk-yjoDCnyx8g4jW_Lk3qynGV1cCuEOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Monday, January 30, 2023, ron minnich <rminnich@gmail.com> wrote:
> I did not want to disrupt the FD 2 discussion, but I could not really let
> this comment go unanswered:
>
> "Smells like C++ to me. Rust in essence is a re-implementation of C++ not
> C. It tries to pack as much features as it possibly can. "
>
> It's hard for me to see how you can say this if you have done any work in
> Rust and C++.
>
> But, short form: Rust is not C++. Full stop.
>
> I did not feel that comment should go unanswered, lest people believe it.
>
Well, I will stand by my opinion, but perhaps you misread what I meant. I
meant that as a whole Rust resembles more C++ than C. Technically it might
lie in between C and C++, but the amount of "features" certainly bring it
closer to C++. While it might be easier to write safer code in Rust than in
C++, I still think that its "weird" syntax and feature bloat make me
dislike it the way I dislike C++.
Just my .02. YMMV.
--Andy
[-- Attachment #2: Type: text/html, Size: 1342 bytes --]
next prev parent reply other threads:[~2023-01-30 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 17:24 [TUHS] " ron minnich
2023-01-30 18:47 ` Andy Kosela [this message]
2023-01-30 18:59 ` [TUHS] " segaloco via TUHS
2023-01-30 19:35 ` ron minnich
2023-01-30 21:37 ` Stuff Received
2023-01-31 1:47 ` Alejandro Colomar
2023-01-31 2:55 ` Dan Cross
2023-01-31 3:59 ` ron minnich
2023-01-31 12:26 ` Dan Cross
2023-02-01 0:40 ` Steffen Nurpmeso
2023-02-01 0:49 ` Larry McVoy
2023-02-01 1:03 ` Luther Johnson
[not found] ` <EjVurdhKm6O8BZ9n0FesPIsZH6sArmVbEN_ikfso8aNlawWIe8ElCGwgaT4ydoWHMNvRty9jDPxFxhLXVXGMjwsTfmfgLgKXcfjpLmqENT8=@protonmail.com>
2023-02-01 2:22 ` [TUHS] Re: yet another C discussion (YACD) Warren Toomey via TUHS
2023-02-01 0:50 ` [TUHS] Algol rules: was something about Rust is not C++ Will Senn
2023-02-01 1:18 ` [TUHS] " Chet Ramey
2023-02-01 1:24 ` Luther Johnson
2023-02-01 0:53 ` [TUHS] Re: yet another C discussion (YACD) and: " Steffen Nurpmeso
2023-02-01 16:34 ` Luther Johnson
2023-01-31 14:15 ` Blake McBride
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=CALMnNGiXVeqBznYwhPmwR-jUtq2OMO64HHc2A4F0o+PFJMu3Fw@mail.gmail.com \
--to=akosela@andykosela.com \
--cc=rminnich@gmail.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).