chisel
cats
chisel | cats | |
---|---|---|
25 | 43 | |
3,717 | 5,177 | |
1.1% | 0.5% | |
9.7 | 8.8 | |
8 days ago | 6 days ago | |
Scala | Scala | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
chisel
-
Calyx: Intermediate Language for Hardware Accelerators
My first instinct was to ask "Does this play well with CIRCT?" And thankfully they answer that right away in the README.
I'm personally of the opinion that there is a LOT of room for improvement in the hardware design tooling space, but a combination of market consolidation, huge pressure to meet deadlines, and an existing functional pipeline of Verilog/VHDL talent is preventing changes.
That's not to say "Verilog/VHDL are bad", because clearly they've been good enough to support nearly all of the wonderful designs powering today's devices. But it is to say, "the startup scene for hardware will continue to look anemic compared to the SaaS scene until someone gives me all of the niceties I have for building SaaS tools in software."
A huge amount of ideas (and entire designs) start off as software sims, which enables kernel/compiler engineers to start building out support for new hardware before it's manufactured.
There is some interesting work going on at SiFive building hardware with Chisel[1], as well as some interesting work lead by a professor at William and Mary to improve simulations[2].
1: https://www.chisel-lang.org
2: https://github.com/sarchlab/akita
- Chisel: A Modern Hardware Design Language
-
I may be creating an abomination
Inspired by Scala. Which can do a whole lot more, and worse. The currently biggest competitor to decades old hardware description languages is a Scala DSL.
-
An addressable little explored language gap: HDL - Hardware Description Languages, any language used for electronic circuit design, description, and specs
Already mentioned Chisel: https://www.chisel-lang.org/
-
Trying to learn and work with FPGAs
I'm also a hobbyist. There are a number of alternative HDLs out there, and as hobbyists we can deviate more from the mainstream of (System)Verilog and VHDL if we desire, though you'll still need to be able to read them. In the past I've done Verilog, but lately I've been using SpinalHDL and have been really enjoying it. Its close relative Chisel also makes appearances in the RISC-V space.
- Alternate HDL language and Physical Design/EDA tools?
-
Learning VDHL after knowing Verilog
What are your thoughts on other HDLs like Chisel or BlueSpec when it comes to better type checking?
-
Learning Verilog and FPGA
I started playing with FPGAs and HDLs a couple years ago with no hardware design background (I'm mostly a software architect/engineer) and in the end found that a "higher-level" HDL suited me better.
I chose Chisel (https://www.chisel-lang.org/) an HDL based on Scala (technically a Scala DSL) which can provide many facilities to hardware generation.
I'd highly advise looking into it although also knowing Verilog helps a lot.
-
If you keep clicking "Give 15 seconds" on Lichess, eventually it overflows to a negative number and you win
But some go further and ask "what if when we add a soldering station on top of it?"
-
What universities have good PhD programmes in digital design?
In recent years Chisel HDL, RISC V, and SiFive came out of their architecture group, to name a few.
cats
-
Beware of teammates who refactor code based on personal taste without proper documentation or completeness. Sounds familiar.
A functional programming library: https://typelevel.org/cats/
-
Is Scala worth learning in 2023?
Learn something that pays the bill first - nowadays it's Golang/Rust react/typescript. Then you can try some pure fp libs like fp-ts and fp-core.rs, and look through existing scala cats docs. If you'll feel bad about it - that's totally fine and expectable, fp takes a paradigm shift and not that many dev able to shift their brains way of thought due to basic psychological rigidity) (inability to change habits and to modify concepts/attitudes once developed). And that's purely a staffing and management issue - folks hired randoms out of the blue, and called 'em a team.
-
Going into year 2 of Software Development Foundation Degree, have a particular liking for OOP and SQL, any tips, info or pointers on where to go from there?
I'm sorry, but have you ever done functional programming for a real company, like in a functional programming language like Haskell, Scala, or F#? Have you ever used Scala cats or scalaz? Have you ever learned category theory and how to apply its abstractions in software? Listen u/judethedude2106 this person hasn't gone as far down the functional programming rabbit hole as I have. Beyond learning the basics like the difference between pure and impure functions, what are closures, what higher order functions are and the most common ones like .map, .filter, and .flatmap, the immutable collections like immutable linked lists and trees, and what a Monad is and common monads like those used for futures/promises, async programming, and Option (Some or None, which is used instead of null checking), the more advanced functional programming stuff like category theory based abstractions are totally useless for real jobs and is just a giant time suck. Don't waste years on functional programming, spend at most a few months on it and no more.
-
rsmonad: Monads in stable Rust (+ Applicative, Alternative, Functor, Monoid, ...)
As a former functional programmer in Scala, please do not go deep into the Category Theory programming. Scala has libraries like this one called "Cats", a cute shortened name for "Category Theory", but code that makes heavy use of these constructs is not understandable to other programmers. Other than using Monads as a design pattern for things like Options (which can be "Some" or "None"), Futures or Promises (which is used for asynchronous programming), and a few other things, please do not make heavy use of category theory constructs in real programming projects that will have other developers working on them. It is a rabbit hole that may be fun but is not super practical. Sure, write pure functions without side effects, but do not use the words "Bimonad", "Invariant Monoidal", and "Semigroup" in your code. The most common, practical application/use of functional programming is basic things like closures, .map, .filter, maybe chaining maps with like a .flatmap or whatever your programming language uses instead of chain or flatmap, and SQL that uses keywords like WHERE which can be represented in code by using a call to .filter. Like the place where these constructs are used most is in data processing like with SQL, ETL (Extract Transform, Load) jobs, Java's MapReduce on Hadoop, Scala's Apache Spark, and other data processing type things. Haskell is not a popular programming language in real world projects for a number of reasons and one of them is the heavy and sometimes impractical use of Category Theory.
-
Tmux, NeoVim, etc. to write pure Kotlin code?
At a previous job of mine we actually had an entirely pure Scala ecosystem using cats which instead uses typeclasses, referential transparency, and other FP concepts as the foundations for how to code. So a lot of flexibility to the language.
-
[E => *] Type
Thanks! It's used heavily here
- for comprehension and some questions
-
Ask HN: How has functional programming influenced your thinking?
I did work in Scala for a few years. We employed Cats[1], and even a bit of Matryoshka[2] though most of the work I do today is in Python.
Nowadays I think about computational requirements in terms of relations among behavioral dependencies. Like, "I want to perform operation O on input A and return a B. To do this, I'll need a way to a -> b and a way to b -> b -> b." I often pass these behavioral dependencies in as arguments and it tends to make the inner core of my programs pretty abstract and built up as layers of specificity.
Zooming out nearly all the way, it makes me feel tethered in a qualitatively unique way to certain deep truths of the universe. In a Platonic sense, invoking certain ideas like a monad make me feel like I'm approaching the divine or at least one instantiation of a timeless universal that operates outside of material existence.
I'd imagine some mathematicians might see the universe in a similar way - one where immortal relations between ontological forms exist beyond time and space and at the same time can be threaded through the material world by intellectual observation and when those two meet a beautiful collision occurs.
1. https://typelevel.org/cats/
2. https://github.com/precog/matryoshka
-
yet another post about type classes in Scala
Our second type class example attempted to illustrate one last perk: type safety at compile time. It did so with a simplified example of the cats core library for type safety equality comparison between objects. If you're not familiar with cats, go ahead and give it go.
- What are the design principles of Cargo?
What are some alternatives?
SpinalHDL - Scala based HDL
Scalaz - Principled Functional Programming in Scala
myhdl - The MyHDL development repository
Shapeless - Generic programming for Scala
amaranth - A modern hardware definition language and toolchain based on Python
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
cocotb - cocotb, a coroutine based cosimulation library for writing VHDL and Verilog testbenches in Python
ScalaTest - A testing tool for Scala and Java developers
skywater-pdk - Open source process design kit for usage with SkyWater Technology Foundry's 130nm node.
Monocle - Optics library for Scala
bsc - Bluespec Compiler (BSC)
Scala Async - An asynchronous programming facility for Scala