chip8-book VS reanimate

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.

Reanimate sounds almost ideal, with its support for LaTeX. But unfortunately, it is all rendered in batch, not providing for any interactivity.

Is this the discussion you're referring to? https://github.com/reanimate/reanimate/discussions/210

It's actually pretty interesting to read. The author makes a not totally unreasonable argument as for why it uses unsafePerformIO.

Now what I'm really curious about is why the very first example on the site I clicked into the source code for, a simple 59-line example, is using unsafePerformIO. That actually worries me more because it suggests that as a user I might have to use unsafePerformIO. https://github.com/reanimate/reanimate/blob/d4d3898831edb4aa...

Not really dashboard library, but reanimate is a good library for this kind of stuff.

Some other "applications" (if you're not interested in compilers) might be writing shell scripts: https://hackage.haskell.org/package/turtle Or animating stuff: https://github.com/reanimate/reanimate and https://hackage.haskell.org/package/gloss

That aside, it seems that svg-tree doesn’t support filter elements, so I recommend reanimate-svg. You can join the Discord server for Reanimate and ask for help. Good luck.

See also reanimate, a very similar Haskell library: https://reanimate.github.io/

This is very niche, but something I've wanted to do for a while is to generate some cool physics example on the surface of a sphere with https://hackage.haskell.org/package/hamilton, and display it with https://reanimate.github.io/ (using https://hackage.haskell.org/package/linear for the projection)

Hi u/Target_Organic, I wich you a warm welcome! Haskell is often very satisfying to work with, it has a sense of beauty in it. Regarding your questions: 1. I never had big problems about performance. However, I personally place more emphasis about correctness, simplicity and readability of my programs. Performance tuning comes after. 2. For graphic libraries, I know diagrams, Reanimate and Haskell-chart. Since you seems interested by mathematical approach to graphics, I think you will find happiness there. 3. I'm not sure about the AI field. Other, more practical languages such as Python seems to have taken the lead. What is sure for me, that Machine Learning/NN would be nicely describe in Haskell with solid foundations.