Did you dry brine? That always seems to be the key for me
06.01.2026 15:58
👍 1
🔁 0
💬 1
📌 0
Did you dry brine? That always seems to be the key for me
Ah, gotcha.
You can have separate abstractions for behavior and style, no?
And now the CI environments need the new version of wasm-bindgen-cli before we can release again.
Ahhh this is giving me ptsd of having to explain to my boss that I have to burn a day updating the web app because someone decided to update the workspace wasm-bindgen version.
Unwrap is code smell.
If I leave an unwrap in my code it feels like an itch until it’s removed.
TIL you can search by function signature, type, etc in #Rust docs: doc.rust-lang.org/rustdoc/read...
RA can be a pain to get going but once you do it makes everything worth it.
Nice post!
I’ve long held that every dollar spent on faster CI and also *one click deployment* is justified. And yet, none of the orgs I’ve worked in have shared that belief, except the one where I got to own all of that.
If anyone has suggestions on tooling or vendors, I'd be happy to hear them.
There's always a trade-off about when to put in the work to make something production-ready. I'm just one dev so I'm not going to worry about scaling for many users or many developers, but I do want to optimize for maintainability and adaptability early on.
I recognize the conventional wisdom is probably to "just start building" the application logic and worry about cleaning up deployment infra later. I'm hoping if I am intentional about designing these deployments it will pay off in increased throughput sooner than later.
I haven't really used terraform or its competitors. At first my app will just be be some static web assets, a single api server, and a Postgres db. I was planning to use GH pages, fly.io, and Supabase respectively, but I may need to put everything on aws for the terraform support.
Thinking about #pivotapp, a full stack web app template I'm building with #rustlang. Reuse is important (it is a template) but there are a few components, and they may be deployed on different platforms. I don't want to have to re-create these deployments again, so I think I need #terraform.
I started a project with ssr and ended up ripping it out. I don’t plan to use it this time.
This is basically what I was building at my last job.
bsky.app/profile/well...
Perfect! Thank you
Nice. I’m interested in using leptos+tauri for those same targets.
Have you done that?
I saw in the last month or so someone posted on bsky a review of all the #rustlang UI frameworks but now I can’t find it.
Are you talking about a native mobile app with leptos+tauri?
Thanks!
I really like leptos. My only concern is that I would like to preserve the option to provide a mobile experience, possibly through the app stores. At one point Leptos worked with Tauri. I might also try shipping the Leptos app as a PWA before I give Dioxus a look.
I'm thinking leptos, axum, and sqlx on top of postgres.
Although I'm also curious about providing a mobile experience, something I have very little knowledge of.
I'm not sure if this will be just a side project, or something I will try to leverage into a job, contract work, or even a business. I think it will be a valuable experience regardless, and I'll do my best to broadcast the journey here.
#webdev #softwaredevelopment #leptos #pivotapp
I have an idea of what I want to build, but I'll probably start with just the infrastructure. Starting with the generic bits will allow me to pivot, or easily start subsequent projects with the same stack. Solving non-domain specific challenges may also be more relevant to the community.
I think I'll build a web app. Building an app from the ground up will allow me to take stock of the #rustlang web ecosystem, which I suspect has come a long way since I got my last job. I am also more resourceful with web tech now, and this will give me an opportunity to continue to #buildinpublic.
I’m in Houston
