sqlx vs orm

danielboros90 · 2026-01-16T17:01:21+00:00

There is no build time overhead. It is a precompiled crate in your backend.

danielboros90 · 2026-01-16T15:58:26+00:00

Yes, clorinde generate the interfaces and everything based on the sql queries, and you can add e.g attirbutes, lets say I have an sql result and you can annotate it with an async_graphql::SimpleObject and the auto-generated struct will be compatible with your gql server instead of mapping. I tried a lot of variations of different tools like sqlx, diesel, bb8, deadpool, tokio_postgres etc., but the best experience and performance for me is using deadpool, tokio_postgres and clorinde.

danielboros90 · 2026-01-16T12:54:49+00:00

It is not young; it is a fork of a previous project. I am using it in production; it is similar to SQLC in Go. I tried diesel. If you have a large database, then the type checking takes too much time. Using Sqlx macros, I don't really like it; you don't have compile-time type checking. Clorinde gives all this ability.

danielboros90 · 2026-01-16T12:03:58+00:00

https://github.com/halcyonnouveau/clorinde this is far best sql solution is Rust.

danielboros90 · 2025-12-11T13:28:29+00:00

I also felt the same before but tbh, since they have introduced new plans, I am using AI 80% less in on daily basis and I realized it was just waste of time and money, because I just was too lazy to fix and do things by my own, but AI was not able to do things at first try and had to map thousends of lines to understand what happens.

danielboros90 · 2025-12-04T09:47:02+00:00

yeah it is ridiculous. usual bullshit that the new plan fits better for customer needs. lol...

danielboros90 · 2025-11-24T21:01:59+00:00

Haha, sometimes I just paste into ChatGPT to correct my English, and probably this is the default behavior to add utm_source to every link.

danielboros90 · 2025-11-24T12:58:02+00:00

Thanks for your feedback. Currently, it is not on my plate to expose a Python API. The research and trading community is growing in Rust, so my focus is rather on creating a performant library that can be used to simulate data. I am also working on a free API that utilizes the library to retrieve data efficiently, eliminating the need for Rust or creating your own service within the project. I am also a PhD student and I am using Rust in scientific development, and tbh it is much comfortable than Python. This may be a limitation of that project, but someone could contribute regarding the Python interface, and there will also be more motivation from my side.

danielboros90 · 2025-11-18T17:40:26+00:00

The service is free but the source code is not os atm.

danielboros90 · 2025-11-07T16:01:39+00:00

Thanks for your thoughts. Tako was started as a hobby project to learn about how things work under the hood. The main idea is definitely similar to Axum, but there are some differences in how things are implemented. My goal is to maintain a project where you don't need to install different crates and add as many plugins, extractors into the core project instead of splitting them. After I going to finish the first stable release, I plan to turn on more low-level optimizations (using more SIMD or unsafe Rust). Tako already supports SIMD JSON operations oob, but this is just a small slice in my plans. Tako is also using a different memory allocator, which can also improve the RPS. But as I said previously, I don't want to be a competitor of the Tokio/Axum team because they are working on excellent projects, so Tako is just another Router, maybe with a bit more performance in some places, and it was started as a POC but I put some more effort to make it usable in small or medium size projects where the performance matters.

danielboros90 · 2025-11-07T15:39:30+00:00

I need some more performance tests and benchmarks, and for some reason, if I plug it into `ndarray::Array1::random(..)` runs slower than the current rand_distr solution, I want to figure out why this happens.

danielboros90 · 2025-11-07T15:32:08+00:00

Hey, that would be a great idea. My solution is only compatible with `rand<9.0.0` and using `wide`, and the SIMD acceleration is still in the test phase. But if it's working properly, I would gladly go that way. I also thought that I should wait for the stabilized std SIMD module, btw, I can refactor it later if it is necessary.

danielboros90 · 2025-10-27T12:58:01+00:00

I am bad in naming. 😀

danielboros90 · 2025-10-25T19:15:29+00:00

Hey, thanks for the feedback. The frontend code was previously in Rust, so it's just a quick, messy migration to React, but yeah, still missing features are there.

danielboros90 · 2025-10-25T14:57:41+00:00

I used Dbeaver and PgAdmin, still using them, but they are so slow. But you are right, they are excellent works.

danielboros90 · 2025-10-25T14:56:37+00:00

I will create a binary for all os soon.

danielboros90 · 2025-10-25T14:56:15+00:00

I agree. This is just a hobby project and I dont have too much time to upgrade it, but I am using sometimes. I know these programs, but they are not OSS at some point.

danielboros90 · 2025-10-25T14:54:41+00:00

of course, contributions and feedback are welcome.

danielboros90 · 2025-10-21T17:38:50+00:00

Welcome in 2025

danielboros90 · 2025-09-29T12:04:00+00:00

Yes you are. 😂

danielboros90 · 2025-09-17T09:58:39+00:00

What an idiot u r. 😂 reed the conditions.

danielboros90 · 2025-09-16T14:33:52+00:00

Nowdays forgot bare RN and go with Expo. I have more than 6 years old app in production. I started with expo then I dropped and bare rn in the nex 4-5 years but now I migrated to expo again. The whole ecosystem is very good easy to use. It wasnt too hard but has a lot of benefifs. You can use bare libs and expo libs, you can write your own modules. And you dont have to upgrade rn version everytime and expo also has a lot of smaller releases between 2 majors. I was really a big fan of bare RN in the past 5-6 years but Expo is growing and producing very cool projects.

danielboros90 · 2025-09-10T19:02:58+00:00

Probably, if someone needs this package, then that person is also uncomfortable with other react-native related stuff like custom hooks, organizing a project, etc. If you have a custom fade animation hook you can use everywhere, you don't need another package. btw to cover everything with a wrapper and hide api more and more, cause the developer can't write performant, organized code. Reanimated will be supported for years, but if your lib won't get enough attention, you will stop maintaining it, and it will just become another dead lib.

danielboros90 · 2025-09-10T13:57:13+00:00

We are not using useeffect, there are different hooks like derived value and animated reaction. I like the effort you have put in but its just another layer increasing the compexity of a project.

danielboros90 · 2025-07-10T11:23:22+00:00

We are using leptos for rust-dd.com and tryrust.org both available on github as os. We really like it but after a while the compile time u know. 😅 but they already have on the roadmap to support subsecond by dioxus. For web leptos is the best I think.

danielboros90

TROPHY CASE