Lightnews — Scholar-powered news

Dusty Pomerleau

@dpom.bsky.social

130 followers 160 following 530 posts

Web hobbyist • Leptos, Axum, Gel (he/him)

Posts Media Videos Starter Packs

Dusty Pomerleau @dpom.bsky.social · 28m

I think specialization is very useful, though I'm not knowledgeable about all the pitfalls. Even in my simple Rust code I was recently trying to implement a trait for T: AsRef<str>, but I wanted a unique impl for PathBuf, and the compiler wouldn't allow it (at least, not without the feature gate).

Reposted by Dusty Pomerleau

Stein Makes Games ➡️ #GodotFest @steinmakesgames.bsky.social · 4d

There's really only two file formats

Calvin and Hobbes comic. Dad explains there's only two types of file formats: .txt and .zip

#programming #software #softwareengineering

Dusty Pomerleau @dpom.bsky.social · 3d

Safari SVG filter bugs completely sap my energy. Just slowly, inexorably, progressing from "this effect is incredible!" to "my head is now on the desk..."

Dusty Pomerleau @dpom.bsky.social · 6d

Knowing the exact reason does matter, because maybe I'm throwing compute at a problem I could solve just by modifying the dockerfile. Ops/infra is a blind spot for me.

Dusty Pomerleau @dpom.bsky.social · 6d

I'm definitely interested in learning to manage it for the future, even if I won't use that specific provider. It was exiting with "status code 2." I couldn't find anything in Render's docs to tell me what that meant.

Dusty Pomerleau @dpom.bsky.social · 6d

But to answer your question:

`time podman build .` in a VM with 8 CPU and 2 GB memory:
515 secs

`cargo clean && time cargo leptos build` using my full machine (Apple M4 Max Macbook Pro with 64 GB memory):
78 secs

Dusty Pomerleau @dpom.bsky.social · 6d

Well there *are* logs, but there weren't any errors - it was just freezing, followed by a nonspecific exit code. I think the platform probably understood the problem, but I wasn't seeing those logs, just the logs from the container, if that makes any sense.

Dusty Pomerleau @dpom.bsky.social · 6d

My favorite thing in the entire world is when a company puts all of the settings for their app on a single, scrollable page.

Dusty Pomerleau @dpom.bsky.social · 6d

It's too early for me to comment on real-life usage costs, but the things I'm building aren't expecting massive scale—for me it's clearly a win.

Dusty Pomerleau @dpom.bsky.social · 6d

If we assume that my app could run on a Starter instance on Render, but that I can't build on the standard pipeline, then I would need to spend a minimum of 19 + 25 + 7 = 51 USD/month just to get the app live, something I can do for 5 USD + usage costs on Railway.

Dusty Pomerleau @dpom.bsky.social · 6d

Getting a better build pipeline on Render requires both the Professional workspace (19 USD/month) + an additional 25 USD/1000 minutes of build time. In contrast, Railway is basically giving away their build pipeline for free.

Dusty Pomerleau @dpom.bsky.social · 6d

Of course usage costs depend on...usage, but getting 8 GB memory on Render requires a ProPlus instance (175 USD/month), and getting 8 CPU requires a ProUltra instance (450 USD/month). Obviously the exact CPU/vCPU specs matter.

Dusty Pomerleau @dpom.bsky.social · 6d

That breath of fresh air with the build pipeline prompted me to compare the instance costs for the server: Railway's Hobby plan offers (up to/on demand) 8 GB RAM and 8 vCPUs, with base pricing of 5 USD, and the rest based on usage.

Dusty Pomerleau @dpom.bsky.social · 6d

I eventually deduced (no thanks to the logs) that the deploy was just running out of memory. This prompted me to try deploying to Railway. The app deployed fully in < 10 minutes, without issues.

Dusty Pomerleau @dpom.bsky.social · 6d

I was trying to deploy my app to Render using a Dockerfile, and their standard build pipeline was taking 2-3 hours to compile and deploy (ultimately failing). This was even after upgrading my workspace to Professional (19 USD/month) and my server instance to Standard (25 USD/month).

Dusty Pomerleau @dpom.bsky.social · 6d

Leptos apps are efficient at runtime, but type complexity can lead to a lot of memory use during compilation, and they have the usual compile time CPU demands of any #RustLang app, so the resource-intensive bit is definitely deployment.

Dusty Pomerleau @dpom.bsky.social · 6d

I rarely give this kind of commercial praise, but @railway.com is knocking it out of the park with their infra pricing model. Here's a little case study from deploying my latest web app:

Reposted by Dusty Pomerleau

dan @danabra.mov · 6d

i think the only way for atproto to succeed is for us to show what apps can do when every app sees every other app's public data, and they share an identity system. no technical or sociological argument is as convincing as seeing seamless interop and the lighthearted competitive landscape it unlocks

Dusty Pomerleau @dpom.bsky.social · 7d

How many times in one lifetime can my build fail because OpenSSL requires Perl.

Dusty Pomerleau @dpom.bsky.social · 7d

Are you using DaisyDisk? It really helps you find the high-yield deletions in this situation.

Dusty Pomerleau @dpom.bsky.social · 7d

Do you really only have 256? I feel like you need to treat yourself to a proper dev machine :)

Dusty Pomerleau @dpom.bsky.social · 7d

This is why everyone is switching to jj though. Why keep track mentally of which actions are destructive when you can just make all actions non-destructive?

Dusty Pomerleau @dpom.bsky.social · 8d

These are my favorites:

kprepublic.com/products/nov...

but I don't think it's an ongoing collaboration, so when they run out I think that's it. I lubed them with tribo and it's a very easy press.

Novelkey Kailh Hako Royal Violet Switch RGB SMD pink Tactile 50g Switc

HAKO ROYAL SWITCHES A collaboration between Input Club and NovelKeys that features a combination of Hako and Royal switches. The switches contain the stem, spring, and top housing from the Hako switch...

Dusty Pomerleau @dpom.bsky.social · 8d

Buttondown is the last email platform you'll migrate to. We're focused on your success, not on bleeding you dry.

Dusty Pomerleau @dpom.bsky.social · 8d

When I first started with #RustLang, I had the impression that dynamic dispatch was very costly at runtime, but my actual observation is that experienced rustaceans use dynamic dispatch all over the place, and seem completely unconcerned about it. I now wonder if I should embrace it more often.