gbench VS mos

It looks like gbench creates trace files that are then opened in Chrome: https://github.com/maksimil/gbench

Github: https://github.com/maksimil/gbench

I'm working on my first crate. It's a tracing tool: https://github.com/maksimil/gbench

Interesting! I wrote an assembler for the 6502 a while ago that works along the same lines. It supports running unit tests from the command-line, has a built-in 6502 emulator, uses the language server protocol to allow refactoring and syntax highlighting in VS Code and even hooks the VS Code debugger up to Vice.

Still working on mos, my 6502 assembler + toolchain. I've spent some evenings getting up to speed with the Debug Adapter Protocol, which allows me to provide a debugger in supported IDEs (like Visual Studio Code). Currently I'm wiring up the VICE emulator to this.

I've just released version 0.2.0 of MOS, my assembler for 6502 CPUs. Apart from spending some additional time on docs, I've spent most of my time on building a Language Server and an initial VSCode extension that supports things like syntax highlighting, find definition, formatting, etc.

That CPU is still going strong. In fact, I'm currently building an assembler for the 6502 in Rust.

https://mos.datatra.sh

I just released version 0.1.0 of my 6502 assembler/formatter called MOS! Really happy about it, since it's the first side-project I've actually managed to get to this state in a VERY long time.

Having said that, you're welcome to follow the repo on GitHub.