chip8-book VS three-layer

Not to discourage you, but there's already a CHIP-8 book in progress: https://github.com/aquova/chip8-book

WASM support would be so cool. There are lots of guides online which could help you out. I saw a guide for the chip8 and it didn't even look too difficult, you can check it out here https://github.com/aquova/chip8-book

Recently I've decided to learn low level programming with Rust. I asked for some projects to practice and got recommened to make a Chip8 emulator. That sounded fun so I searched a bit and found this guide that walks you step by step.

I made some emulators in Rust as a learning project during the start of the pandemic, and ran into the exact same issue when I wanted to make a wasm version to run in a browser. Eventually, I was able to figure out how to do it, although I do use the 'wasm-pack' Cargo package to assist with it (I think you can get away without it if you're really motivated, you just need to set up the targets and other elements yourself). Basically you define some Rust API to expose whatever you need from your project, then that and the project get compiled into one .wasm binary and some (surprisingly readable) JavaScript "glue" gets generated which allows for easy inclusion into a web page. It works well for code in the std, but I've had issues with 3rd party packages.

It's focused on emulation development, but I wrote a document that describes the process I followed: https://github.com/aquova/chip8-book/blob/master/src/wasm.md

I followed [this](https://github.com/aquova/chip8-book) book which uses Rust.

I’m working on this pet project for a time now. Initially based on the three-layer repository, it’s now modelled after the Clean Architecture. In my understanding, it’s an OOP variation of the functional “Functional Core, Imperative Shell” approach. As most examples for Clean Architecture are written in C#, my module structure also looks more like a typical C# than Haskell one to me.

I personally use servant whenever i need networking. Altough scotty is easier/simpler, I would start with scotty. Aeson for JSON encoding/decoding. Actually! As i am writing this I would recommend a book (no its not a dry boring book, more of a tutorial) that implements a CI server from scratch. It’s vety descriptive and will show you the haskell ecosystem quite clearly: https://marcosampellegrini.com/simple-haskell-book. Seriously, it’s a damn good book and that’s how i learned haskell! Back to the libraries/ecosystem, if you want to learn how to use an app monad and mtl, these who come to mind: https://github.com/Holmusk/three-layer and https://www.parsonsmatt.org/2018/03/22/three_layer_haskell_cake.html. Under the github repo, check out the App folder to get a notion of how an app monad can be used. Personally I like mtl over monad transformers such as readerT. Best of luck!

I usually make web apps in haskell + react, when i started out learning haskell I found it invaluable to find a opinionated stack to learn about the ecosystem and to see "how to get things done". When i was learning haskell I really appreciated an example like: https://github.com/Holmusk/three-layer, essentially a "best practice" web app. Anyone in the clojure(script) community that can recommend some templates/examples to get to know the ecosystem? Since im comfortable with react im assuming clojurescript with re-frame/reagent makes sense for the frontend? So far i've only seen ring/jetty for the backend. To be clear, im not necessarily looking for the "simplest" frameworks but rather something that is highly reliable in production. The backend will expose simple JSON crud with some endpoints being quite computationally heavy (concurrency will be important).

In Haskell, Matt Parsons popularised the Three Layer Haskell Cake (2018). Holmusk (well, Kowainik) made this picture to go along: