mos VS diesel

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.

7. Diesel

Both seem nice. However, both of them rely very heavily on prepared statements. Unfortunately, using prepared statements is a no-go when you use connection poolers like pgbouncer, or in my case AWS RDS proxy. A discussion in Diesel indicates that disel is not going to provide any support for disabling prepared stements (https://github.com/diesel-rs/diesel/discussions/3575), and a discussion on sqlx hints that disabling prepared statements is possible, but I haven't found any documentation or examples for it.

In addition we are experimenting with prebuild versions of diesel-cli that can be installed directly. We have a set of prebuilt binaries here. We are interested in feedback about how the provided binaries work on your platform.

First of all thanks for making this great tool. As it happens I currently toy around with using it for diesel-cli releases. See the WIP PR here. I think diesel-cli is a good example of a tool that depends on system libraries as it needs to link native database drivers, so this new release is welcome. Defining the dependencies seems to allow easily building things on x86_64-unknown-linux-gnu and x86_64-apple-darwin. It seems to pick up everything in the right way there.

I did look at mysql initially. Then I started checking other crates. Diesel is an Object Relation Model (ORM), I'm not yet keen on taking on the complication of learning ORM, I give this crate a pass in the meantime.

I would recommend people look at diesel from Rust for how nice it could be. https://diesel.rs/ Look at the complex queries example. So much more readable and easier to understand.

Most wanted missing features in diesel

There are two problems with using Rust for web servers:

1. The only production-ready Rust web servers require writing async request handlers. Async Rust is not fun.

2. The only good Postgres client library is async: https://crates.io/crates/sqlx

I'm trying to remedy the first problem with https://crates.io/crates/servlin .

Solving the second problem will be another project. I hope someone else does it. There is https://crates.io/crates/diesel but it has the same problem as async Rust: incomprehensible compiler errors.

Lemmy is written in Rust using Actix Web and Diesel.rs.

https://actix.rs/

https://diesel.rs/