bubbles VS diesel

I recommend looking at the charm libraries. Lip gloss https://github.com/charmbracelet/lipgloss can provide the styling and bubble tea can handle the screen updates and framework https://github.com/charmbracelet/bubbletea there is a premade progress bar component in bubbles library. https://github.com/charmbracelet/bubbles

nhooyr/websocket, shollz/pake, charmbracelet/bubbles, charmbracelet/bubbletea, charmbracelet/lipgloss, muesli/reflow, klauspost/pgzip and many, many more.

You should check bubbletea, bubbles and harmonica

At Charm, we generally use Go for all our libraries like Bubble Tea, Bubbles, and Lip Gloss. Go should be easy to pick up if you know JavaScript and Python. That being said there are also fantastic libraries available for Python (https://github.com/Textualize/rich) and JavaScript as well.

I think you can, but if you're using Go I would recommend using Bubble Tea, Bubbles, and Lip Gloss for better customizability and flexibility (you can also use the gum code as reference).

You picked a good time, too, since the textarea bubble is brand-spanking-new! https://github.com/charmbracelet/bubbles

We started working on Bubble Tea in January 2020 and launched it October 2020! We originally built it for Glow and the mini Charm TUI which developed most of the ecosystem (aka Bubbles.

charmbracelet/bubbles

From a cursory reading of the docs it seems Bubble Tea doesn't implement things like that, but that the author has a "widget" library at https://github.com/charmbracelet/bubbles

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/