awesome-v VS diesel

Clearly plenty of people use it. Project is very active, has over 30,000 stars, and constant releases. Plus: 1.Vlang on Exercism 2. Vlang on Rosetta Code) 3. Awesome V 4. VPM (Vlang Package Manager)

> TIOBE's data is so botched...

Stop deluding yourself. If we take out TIOBE, and use the IEEE's Top Programming Languages of 2022, D is still recognized (even higher than the 30s) while Zig, Nim, or Crystal do not even make their chart. That's the reality.

> Vlang...

To begin with, you are a known troll (with possibly multiple troll accounts at HN) that has spent over an year engaging in slander and lies about the language almost any time it's mentioned.

Looks like you are the creator or involved with some other language that can't get as much support or popularity. It would be advisable for you to stop being obsessed with Vlang. How many years of your life will you waste on such childish antics? You would be better off focusing on making your programming language better, if it's not already too late and its a failure.

As for pushing this bold face lie that the language is a "scam", that's both ludicrous and easily proven false. Vlang has many hundreds of code examples and projects. Easily found at: 1) Vlang examples on GitHub (vlang/V/tree/master/examples). 2) Vlang at Rosetta Code (https://rosettacode.org/wiki/Category:Vlang). 3) Awesome Vlang at GitHub (https://github.com/vlang/awesome-v).

The "scam" is you tricking yourself into thinking that your troll tactics are working. Instead, your continual defamation is making what you are even more obvious.

Where I totally agree with you is about how we can have different interpretations of what this involves. Thus, I kind of go with examples and projects. Awesome V on GitHub, would probably be a good place to find something, if a person wanted to get into some significant projects, but don't know how deep the OP wants to go.

https://github.com/vlang/awesome-v

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/