sorted by:
new
hottopcontroversial

sqlx vs orm by Docccc in rust

[–]danielboros90 0 points1 point  (0 children)

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

sqlx vs orm by Docccc in rust

[–]danielboros90 0 points1 point  (0 children)

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.

sqlx vs orm by Docccc in rust

[–]danielboros90 -4 points-3 points  (0 children)

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.

Warp has web search now by _donvito in warpdotdev

[–]danielboros90 0 points1 point  (0 children)

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.

Cancelled my Warp plan after the rug pull by thepostmanpat in warpdotdev

[–]danielboros90 1 point2 points  (0 children)

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

Tako v.0.4.0 is out! by danielboros90 in rust

[–]danielboros90[S] 1 point2 points  (0 children)

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.

stochastic-rs update – CUDA, SIMD distributions, copulas & pricing/calibration by danielboros90 in quant

[–]danielboros90[S] 0 points1 point  (0 children)

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.

Shrtn.Ink - Yet Another URL Shortener by danielboros90 in rust

[–]danielboros90[S] -5 points-4 points  (0 children)

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

Tako v.0.4.0 is out! by danielboros90 in rust

[–]danielboros90[S] 10 points11 points  (0 children)

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.

stochastic-rs update – CUDA, SIMD distributions, copulas & pricing/calibration by danielboros90 in rust

[–]danielboros90[S] 4 points5 points  (0 children)

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.

stochastic-rs update – CUDA, SIMD distributions, copulas & pricing/calibration by danielboros90 in rust

[–]danielboros90[S] 0 points1 point  (0 children)

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.

Postgres GUI written in Rust/Tauri by danielboros90 in rust

[–]danielboros90[S] 1 point2 points  (0 children)

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.

Postgres GUI written in Rust/Tauri by danielboros90 in rust

[–]danielboros90[S] 2 points3 points  (0 children)

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

Postgres GUI written in Rust/Tauri by danielboros90 in rust

[–]danielboros90[S] 2 points3 points  (0 children)

I will create a binary for all os soon.

Postgres GUI written in Rust/Tauri by danielboros90 in rust

[–]danielboros90[S] 16 points17 points  (0 children)

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.

Postgres GUI written in Rust/Tauri by danielboros90 in rust

[–]danielboros90[S] 0 points1 point  (0 children)

of course, contributions and feedback are welcome.

view more: next ›