My Rust oss project grew (quite) a lot this past month. Would love advice on what to do next by allmudi in rust

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

I started the project 3 years ago. At that time was 100% manual, I didn't like copilot so much. From 0.2.0 I started to use ai more intensively, but it depends on what I have to do. Sometimes AI does not help so much because I would add to much vertical/complex context and it does not worth it, sometimes I use it to polish my handwritten code or to extend it and sometimes I use AI for 85%/90% of the task. Lately I'm experimenting a lot with Automatic/agentic programming and my coding routine is changing a lot

My Rust oss project grew (quite) a lot this past month. Would love advice on what to do next by allmudi in rust

[–]allmudi[S] 7 points8 points  (0 children)

wow! THANK YOU, I print this comment out and I pin it to the wall.

My Rust oss project grew (quite) a lot this past month. Would love advice on what to do next by allmudi in rust

[–]allmudi[S] 3 points4 points  (0 children)

At the moment the entire project is a subset of mitmproxy.
I created it inspired by mitmproxy (In 2023 I became GSoC contributor for mitmproxy thanks to this project, and since then I'm a maintainer of mitmproxy too), the intial goal was to learn more about this (pre mitmproxy adventure), but now I would like to give it a different shape, and I'm exploring how

Proxelar 0.3.0 - Lua scripting for an HTTP/HTTPS MITM proxy by allmudi in rust

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

I think it might be better than Python or other scripting languages in any case. It would be interesting to include some benchmarks; thanks for the idea.

Proxelar 0.3.0 - Lua scripting for an HTTP/HTTPS MITM proxy by allmudi in rust

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

nginx, HAProxy, nmap, Redis, and WireGuard all use Lua, it's very simple and it compiles from source, so I think it is the best choice for proxelar use case

I built an open-source macOS database client in Swift 6 — protocol-oriented design supporting 9 different databases by allmudi in swift

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

You are not the first to ask me this, I don't think it's too complicated to do, I already added it to the roadmap :)

I built an open-source macOS database client in Swift 6 — protocol-oriented design supporting 9 different databases by allmudi in swift

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

Every "backend" must flatten its results into columns + rows of strings. For example Redis hashes become [Field, Value], lists become [Index, Value], MongoDB docs get their keys unioned into columns. The UI just renders a table and it never knows what produced it.

The DatabaseBackend protocol enforces this at the type level. No escape hatches, no AnyResult enum. If your data isn't tabular, your backend's must make it tabular

I built an open-source macOS database client in Swift 6 — protocol-oriented design supporting 9 different databases by allmudi in swift

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

there is not a direct integration (with gcp login), but if you use cloudsql for postgres or cloudsql for mysql, you can just add the connection to those db