Viewing profile — dyogenez

Memcached was a savior for caching when it launched. I love that it was created in 2003 by Brad Fitzpatrick for LiveJournal. Each post on a users feed could have different access r…

Another +1 for Tiller! I'm doing something similar with Tiller (which I've been using since Mint was acquired by Intuit). It's neat to see how OP did this using a Claude Routine th…

One game that changed my life was SimCity 2000. It shaped how I think about building products - before I even knew the term. Just published a new blog post about how it impacted me…

Back when I was a kid, I'd get the monthly Nintendo Power magazine and check out the top games of the month to see what was popular (A Link to the Past was my default vote). I want…

> Why do you need GraphQL here? The app was initially client-side only. I choose GraphQL over REST because Hasura created a super quick API for the database. Also, our API is publi…

Post author here. I've been developing in Ruby and Rails for almost 20 years. Here are some of the downsides in my opinion. - The Global interpreter lock (GIL) in Ruby is less perf…

It's less expensive now with Rails than our hosting was with Next.js. If there was more traffic, we'd save even more money in comparison. That was mentioned in the post.

> You can do this with Next.js SSR Yep! It'd be possible with Next.js. The difference is how it's organized. In Next.js with RSCs, we were fetching data for each part of the page w…

We have one developer (me) and we're bootstrapped and not yet profitable. That means I'm paying the difference every month in hosting and working for free. The site makes it look l…

> Sure, some use-cases might warrant the flexibility that GraphQL uses. A book tracking app does not. I agree! If you're in control of the experience, then I wouldn't choose GraphQ…

Thanks for the comments! You hit on a lot of why our app is structured the way it is. I agree too, we could've put those investments into Next.js rather than migrating to Rails. Th…

That is one of the slower pages on the entire app. I'd like to move that one to use an InertiaRails.deferred setup, so it loads instantly with a loading spinner - like you'd see wi…

I haven't so far. I’ve preferred the new way: With RSCs, I’d have code scattered throughout components that would hit APIs to get data. With Rails + Inertia, that code is all in a …

We recently did a major migration from Next.js to Ruby on Rails with Inertia that took a few months. I wanted to share some of the thought process behind that decision, how we made…

Thanks for the post! I noticed an uptick in referrals from YC for a little while just from this. - Adam, Founder of Hardcover

Really curious about this too. react-rails is deprecated, so the choice seems to be react_on_rails or inertia.js.

Nice! Yeah I like the idea of sharing our static book data here on some kind of cadence. I'll pencil this in by the end of the year.

We usually spend about $60/month at Google anyways, so $100 wasn’t a crazy jump. That could be one left on Cloud Run instance. When it jumped to $300 total after disabling it that’…

I recently had a call with Google and have a sales/solution person I’ve been talking to about moving more services there. I’ll share what happened and see what they say.

This sounds like a solid next step. I’d like to stop storing URLs we don’t control in our DB and share URLs to these images behind a CDN. We could slowly roll that out and update e…

Thank you! I was wondering where the 250ms of latency was coming from. I’ll change this up today.

I think you have it right. The signed URLs are a way to giving people an address to the files from our API, then they have call it again to key the keys. I suspect if once we put t…

I’m going to have to look into this today. I assuming generating the URLs hit an API, but if those can happen fast locally that changes things.