From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] extremely busy crowdsupply update started
Date: Sun, 29 Mar 2020 11:22:44 +0000
Message-ID: <CAPweEDxGrqnZVqrNmu_iTpQJc_bazai80v8QmBBoRqReUKJtEQ@mail.gmail.com> (raw)
In-Reply-To: <24756f54d28bd109e0bf1613acbf868d268e262b.camel@gmail.com>
On Sun, Mar 29, 2020 at 11:46 AM Jock Tanner <tanner.of.kha@gmail.com> wrote:
> On Sat, 2020-03-28 at 17:44 +0100, Jean-Paul Chaput wrote:
> > At this point I have no clear answer about what the "best" language
> > would be. But I can tell you for sure that many "hardware guys" are
> > literally repelled by languages like Chisel.
> > It's a discussion we are currently having at the lab. Like the
> > one
> > that did take place in this list a little while ago.
> > =20
>
> Both Chisel and SpinalHDL are syntactically derived from Scala. Scala
> is a younger, a bit less scary sibling of Haskell. Haskell can scare
> the shit out of every software engineer except those with strong
> mathematical background. So I suggest it's not the best practices that
> repells “hardware guys”, but a careless introduction to functional
> approach in programming.
that, and the fact that the rocket-chip developers (from Berkeley)
claimed to "reduce code size significantly" in the two following ways:
1. pretty much absolutely f***-all in the way of comments.
2. make heavily depth-nested use of classes and mix-ins [with ZERO
documentation].
the first major exposure to a real-world industry-class processor
written with the Chisel system, and it's one of the worst (best)
introductions on how *never* to write (un)maintainable (un)useable
code i've seen in 43 years of programming, with the exception of some
hilarious perl and php scripts.
i'd _really like_ to give you good examples of code written in Chisel: i can't.
the more important thing, than Chisel, is, as Jock points out: scala
simply isn't popular.
https://www.infoworld.com/article/3270626/python-scala-climb-the-ranks-of-language-popularity.html
http://pypl.github.io/PYPL.html
scala remains at 0.97% - less than one percent - by way of how pupular
language tutorials are searched for.
python on the other hand is *right at the top* - with a whopping 30%.
so i know you picked SpinalHDL for vexriscv:
https://github.com/SpinalHDL/VexRiscv
however, i would be particularly interested to hear your thoughts on,
for example this:
https://github.com/SpinalHDL/VexRiscv/blob/master/src/main/scala/vexriscv/plugin/MulSimplePlugin.scala
versus this:
https://github.com/lambdaconcept/minerva/blob/master/minerva/units/multiplier.py
just on an *instinctive* level, which one is easier to read?
from a style perspective: *six* levels of indentation-bracing?
really?? and using "=" to indicate type-declaration (val
aSigned,bSigned = Bool), where every other language uses it for
assigmnent? and the "implicit return result" by assigning to a
variable with the same name as the function? i mean, they should have
made it more difficult than that.
it's just... flat-out.... NO. anyone writing code in this language is
*deliberately* making their life hell, and, worse, if the chip becomes
a commercial success (or an academic success) the insanely high
barrier to entry will make it extremely costly to find programmers.
... lesson learned? :)
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 21:03 Luke Kenneth Casson Leighton
2020-03-27 5:49 ` Jacob Lifshay
2020-03-27 8:47 ` Luke Kenneth Casson Leighton
2020-03-27 21:31 ` Jacob Lifshay
2020-03-27 21:36 ` Luke Kenneth Casson Leighton
2020-03-31 4:18 ` Jacob Lifshay
2020-03-27 14:39 ` Immanuel, Yehowshua U
2020-03-27 15:49 ` Luke Kenneth Casson Leighton
2020-03-27 16:35 ` Tobias Platen
2020-03-27 19:20 ` Luke Kenneth Casson Leighton
2020-03-27 21:29 ` Jacob Lifshay
2020-03-27 21:32 ` Luke Kenneth Casson Leighton
2020-03-28 11:52 ` Luke Kenneth Casson Leighton
2020-03-27 16:56 ` Michael Nolan
2020-03-27 19:21 ` Luke Kenneth Casson Leighton
2020-03-28 8:09 ` Jock Tanner
2020-03-28 10:02 ` Luke Kenneth Casson Leighton
2020-03-28 16:44 ` Jean-Paul Chaput
2020-03-28 17:13 ` Luke Kenneth Casson Leighton
2020-03-31 8:17 ` Jean-Paul Chaput
2020-03-31 9:31 ` Luke Kenneth Casson Leighton
2020-03-31 9:32 ` Luke Kenneth Casson Leighton
2020-03-31 9:38 ` [libre-riscv-dev] pyobjc, gnu objective-c and gnustep Luke Kenneth Casson Leighton
2020-03-31 11:42 ` lkcl .
2020-03-31 14:11 ` Jean-Paul Chaput
2020-03-31 14:30 ` lkcl .
2020-03-31 16:16 ` Jacob Lifshay
2020-03-28 17:14 ` [libre-riscv-dev] extremely busy crowdsupply update started Luke Kenneth Casson Leighton
2020-03-28 23:16 ` Luke Kenneth Casson Leighton
2020-03-29 13:23 ` Jock Tanner
2020-03-29 13:46 ` Luke Kenneth Casson Leighton
2020-03-29 10:46 ` Jock Tanner
2020-03-29 11:22 ` Luke Kenneth Casson Leighton [this message]
2020-03-29 16:05 ` Immanuel, Yehowshua U
2020-03-29 16:26 ` Luke Kenneth Casson Leighton
2020-03-28 18:07 ` Michael Nolan
2020-03-28 18:33 ` Luke Kenneth Casson Leighton
2020-03-31 11:17 ` Luke Kenneth Casson Leighton
2020-03-29 3:14 ` Immanuel, Yehowshua U
2020-03-29 3:15 ` Immanuel, Yehowshua U
2020-03-31 11:26 ` Luke Kenneth Casson Leighton
2020-03-31 18:09 ` Luke Kenneth Casson Leighton
2020-03-31 18:14 ` Luke Kenneth Casson Leighton
2020-04-01 1:51 ` [libre-riscv-dev] name change announcement on crowdsupply Jacob Lifshay
2020-04-01 1:52 ` Jacob Lifshay
2020-04-01 10:57 ` Luke Kenneth Casson Leighton
2020-04-01 17:31 ` Jacob Lifshay
2020-04-01 17:44 ` Luke Kenneth Casson Leighton
2020-03-31 18:35 ` [libre-riscv-dev] extremely busy crowdsupply update started Cole Poirier
2020-03-31 23:11 ` Cole Poirier
2020-04-01 10:08 ` Luke Kenneth Casson Leighton
2020-04-01 10:54 ` 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=CAPweEDxGrqnZVqrNmu_iTpQJc_bazai80v8QmBBoRqReUKJtEQ@mail.gmail.com \
--to=lkcl@lkcl.net \
--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