New week, new Rust! What are you folks up to?
It's a short week, but I've re-written a python application to rust (very simple REST api, but spaghetti none the less). Long story short, it creates databases. Unfortunately realized that sqlx isn't as complete as psycopg is; there's a lot of string interpolation that shouldn't be there.
A second project that's nearing completion (as far as anything is ever "complete") is an application that connects to ~400 different databases and deletes schemas based on the state in 2 other databases. Also uses sqlx, but is being rewritten with a hand-rolled tls connector, because for some reason, sqlx just silently fails when connecting in a k8s environment. No logs at all. Luckily, changing connection pool crate(s) is fairly easy. But still.
Finally, I'm also writing my CRUD recipe app. I wrote a recipe app as a fledgling programmer, but it was terrible (pity I don't have the code left). This one is also terrible, of course, but it's terrible because I'm overengineering everything, not because the tech stack is bad.
1 Like
Usual metaverse client stuff.
-
Plumbing for animation control. The client end which talks to the server has to say some new things to the scene end that talks to the renderer. This takes some ownership and locking planning. Multi-threaded Rust work involves a lot of plumbing like that.
-
Some kind of lock conflict really slows WGPU down when one thread is adding textures and another thread is rendering. I can see the lock conflict with Tracy profiling, but haven't figured out exactly what's going on.
1 Like
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.