Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] benefits of rust
Date: Sat, 14 Mar 2020 19:47:45 -0700
Message-ID: <CAC2bXD7FXkGaZh73qRuzeFYSmCOuA8TcWqgY0TGcDbCO8ARg-Q@mail.gmail.com> (raw)
In-Reply-To: <20200314181350.hahr4ofrf2dmjxz6@topoi.pooq.com>

On Sat, Mar 14, 2020, 11:14 Hendrik Boom <hendrik@topoi.pooq.com> wrote:

> On Fri, Mar 13, 2020 at 10:13:06AM +0000, Luke Kenneth Casson Leighton
> wrote:
>
> >
> > 1). bad: it is seriously demeaning to use the phrase "non-paranoid" -
> > to ACCUSE potential users of rust of "being paranoid".  can i suggest,
> > jacob, raising that as a severe and high-priority issue with the rust
> > community to get that removed effective immediate?
>
> The whole point of rust is that its static checking is reassurance for
> the paranoid!
>

while that's true, Rust does have other benefits over languages such as
Python, JavaScript, Java, C#, C, and C++:
speed, consistency (no GC pauses), native execution, low memory usage,
basically nearly all the gotchas are caught by the compiler at compile-time
(unlike C and C++ and, to a lesser extent, other languages) so if it
compiles then it's likely to work, much more powerful type deduction, the
ability to extend the interface of any type, not needing all the special
cases that come with C++ constructors, vastly improved composability,
accessible and easy to use library ecosystem, very friendly community, much
easier to parallelize code, etc.

Static checking is not just for the paranoid, since the checking enables
programmers to make faster programs by using rust's composability to use
faster more complex algorithms that wouldn't be practically feasible to get
correct in a language such as C or Python.

Here's an example where someone was able to use b-trees instead of the
simpler avl trees because rust's checking and composability meant that it
wasn't extremely hard to get correct (as it would have been in C):
http://dtrace.org/blogs/bmc/2018/09/28/the-relative-performance-of-c-and-rust/

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPweEDyGztErPRa=9KLM9J02R1fLQ9Y23VY7UNAkfJ5yt-03PQ@mail.gmail.com>
     [not found] ` <20200220093921.635c47f72ea2faf85dd352b7@gmx.com>
2020-03-12 14:32   ` [libre-riscv-dev] next tasks Hendrik Boom
2020-03-12 14:43     ` Luke Kenneth Casson Leighton
2020-03-12 17:40       ` Jacob Lifshay
2020-03-13  6:44         ` Lauri Kasanen
2020-03-13  7:38           ` Jacob Lifshay
2020-03-13  8:04             ` Lauri Kasanen
2020-03-13  8:25               ` Jacob Lifshay
2020-03-13 10:13                 ` Luke Kenneth Casson Leighton
2020-03-13 18:10                   ` [libre-riscv-dev] Rustup security Jacob Lifshay
2020-03-14 18:13                   ` [libre-riscv-dev] next tasks Hendrik Boom
2020-03-14 18:23                     ` whygee
2020-03-14 18:28                       ` Luke Kenneth Casson Leighton
2020-03-14 18:49                         ` whygee
2020-03-15  2:47                     ` Jacob Lifshay [this message]
2020-03-15  5:18                       ` [libre-riscv-dev] benefits of rust Hendrik Boom
2020-03-15  5:42                         ` Jacob Lifshay
2020-03-15  5:47                           ` [libre-riscv-dev] [OT] Minecraft garbage collection Hendrik Boom
2020-03-15  6:41                             ` Jacob Lifshay
2020-03-15 12:11                               ` Luke Kenneth Casson Leighton
2020-03-16 13:22                                 ` Luke Kenneth Casson Leighton
2020-03-16 16:22                                   ` Jacob Lifshay
2020-03-16 16:24                                     ` Luke Kenneth Casson Leighton
2020-03-17 18:23                   ` [libre-riscv-dev] next tasks Jacob Lifshay
2020-03-17 18:56                     ` Luke Kenneth Casson Leighton
2020-03-16 18:30         ` Immanuel, Yehowshua U
2020-03-16 18:51           ` Jacob Lifshay
2020-03-16 22:53             ` Luke Kenneth Casson Leighton
2020-03-16 22:53           ` Luke Kenneth Casson Leighton
2020-03-16 23:12             ` Immanuel, Yehowshua U
2020-03-16 23:16               ` Immanuel, Yehowshua U
2020-03-16 23:42               ` Luke Kenneth Casson Leighton

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=CAC2bXD7FXkGaZh73qRuzeFYSmCOuA8TcWqgY0TGcDbCO8ARg-Q@mail.gmail.com \
    --to=programmerjake@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git