Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Introduction
Date: Mon, 15 Jun 2020 18:09:17 -0700
Message-ID: <6FD98A7F-B751-48AE-8829-0CBD38F1CFF6@gmail.com> (raw)
In-Reply-To: <CAC2bXD7coX-Y7fo=BDQ+_Ju3gsZqyJY3w1KS3SLy+UNE9o6Z9Q@mail.gmail.com>


> On Jun 15, 2020, at 3:51 PM, Jacob Lifshay <programmerjake@gmail.com> wrote:
> 
> You may want to learn Rust since it's being used for Kazan (the Vulkan 3D
> graphics driver), as well as an IEEE 754 reference floating-point
> implementation, an algebraic numbers library (basically computing using
> exact real numbers using *lots* of number theory magic; the reference FP
> implementation uses it to do arithmetic), and a few other parts of our
> project.
> 
> Also, I find Rust to be awesome coming from a background in C/C++. No more
> mysterious SIGSEGV or buffer overflows! (had quite a few of those in the
> old C++ version of my Minecraft-like game.) Also, Rust makes it easy to
> manage your source code when building a project since it has an awesome
> package/build manager named cargo. It's the #1 most loved language on
> stackoverflow 4 years in a row for a good reason! (I'll just leave it at
> that for now, I could go on for pages)
> 
> https://stackoverflow.blog/2020/01/20/what-is-rust-and-why-is-it-so-popular/

Hehe Jacob I’m a kindred spirit. While she was writing a google maps clone for school in c++ I tried to help her once or twice and she got annoyed at how many times I got frustrated at simple things like “cout << endl” and said “this would be so much easier in rust!”

> That would be really helpful, currently we don't have a very good solution
> (manually updating pages on the wiki when we remember).

Yes that’s precisely what inspired this idea, Luke and I were talking about Kanban and I started to think of ways we could enhance it to use all of the data from the bugzilla rest API. Too many emails are currently being sent that don’t get raised as bug reports and the whole structure of bugzilla while very useful for discussions, is not good for keeping track of things from a high level. This should eventually help cover budgets and road maps as well. I’ll just be cloning different functionality from various kanban/planner type online services, and adapting them to precisely fit our needs.

Cole
_______________________________________________
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: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:06 Anais Poirier
2020-06-15 20:16 ` Yehowshua
2020-06-15 20:27 ` Luke Kenneth Casson Leighton
2020-06-15 20:27 ` Yehowshua
2020-06-15 20:49   ` Luke Kenneth Casson Leighton
2020-06-15 20:55     ` Cole Poirier
2020-06-15 21:04       ` Luke Kenneth Casson Leighton
2020-06-15 21:08         ` Yehowshua
2020-06-15 21:13           ` Yehowshua
2020-06-15 21:16             ` Luke Kenneth Casson Leighton
2020-06-15 21:13           ` Luke Kenneth Casson Leighton
2020-06-15 22:20           ` [libre-riscv-dev] using debian on a mac Jacob Lifshay
2020-06-16  0:01             ` Luke Kenneth Casson Leighton
2020-06-15 20:58     ` [libre-riscv-dev] Introduction Yehowshua
2020-06-15 21:15     ` Hendrik Boom
2020-06-15 21:17       ` Luke Kenneth Casson Leighton
2020-06-15 22:51 ` Jacob Lifshay
2020-06-15 23:59   ` Luke Kenneth Casson Leighton
2020-06-16  1:09   ` Cole Poirier [this message]
2020-06-16  3:03     ` Jacob Lifshay
2020-06-16  3:30       ` Cole Poirier
2020-06-16  8:50     ` Staf Verhaegen
2020-06-16 10:59       ` Luke Kenneth Casson Leighton
2020-06-16 12:33         ` Staf Verhaegen
2020-06-16 13:13           ` Luke Kenneth Casson Leighton
2020-06-16 18:29             ` Cole Poirier
2020-06-17  6:17               ` Lauri Kasanen
2020-06-17 16:14                 ` Cole Poirier
2020-06-16 12:42         ` Staf Verhaegen

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=6FD98A7F-B751-48AE-8829-0CBD38F1CFF6@gmail.com \
    --to=colepoirier@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