dyogenez

8 ms·

1.
by dyogenez 3mo ago
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 restrictions, and this allowed posts (or entire pages) to be
2.
by dyogenez 5mo ago
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 though. My version locally uses a local qwen mo
3.
From SimCity 2000 to Ruby on Rails: How Games Sparked My Love of Orchestration(adamfortuna.com)
2 points by dyogenez 9mo ago|1 comments
4.
by dyogenez 9mo ago
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. Lately I've been thinking about how the feeling I get
5.
Show HN: I built a trending books by month Bump Chart with Hardcover data(hardcover.app)
2 points by dyogenez 10mo ago|0 comments
6.
by dyogenez 1y ago
> 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 public! We started as an alternative to Goodreads when they cl
7.
by dyogenez 1y ago
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 performant than async thread programming in JS (and some ot
8.
by dyogenez 1y ago
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.
9.
by dyogenez 1y ago
> 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 where it's used (trending books, Live event
10.
by dyogenez 1y ago
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 like we have a lot more together than we are.
11.
by dyogenez 1y ago
> 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 GraphQL for a limited experience either. The project
12.
by dyogenez 1y ago
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. The difference was with Rails I could envision what the e
13.
by dyogenez 1y ago
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 with Suspense + RSC. (Hardcover founder here)
14.
by dyogenez 1y ago
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 Rails controller - usually with a serializer. I’m still
15.
We Fell Out of Love with Next.js and in Love with Ruby on Rails and Inertia.js(hardcover.app)
9 points by dyogenez 1y ago|3 comments
16.
by dyogenez 1y ago
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 it and what the change looked like in practice. Inertia.js
17.
by dyogenez 2y ago
Thanks for the post! I noticed an uptick in referrals from YC for a little while just from this. - Adam, Founder of Hardcover
18.
by dyogenez 2y ago
Really curious about this too. react-rails is deprecated, so the choice seems to be react_on_rails or inertia.js.
19.
by dyogenez 2y ago
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.
20.
by dyogenez 2y ago
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’s when I got worried.
21.
by dyogenez 2y ago
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.
22.
by dyogenez 2y ago
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 each image url in our database over time with both continuing
23.
by dyogenez 2y ago
Thank you! I was wondering where the 250ms of latency was coming from. I’ll change this up today.
24.
by dyogenez 2y ago
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 the files behind a CDN with signed keys, we’ll have even more
25.
by dyogenez 2y ago
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.
26.
by dyogenez 2y ago
Thanks for the comment! Few things to reply to from here. We didn’t have list access enabled, but someone did get a list of files from our API. Rails with Paperclip and active storage is amazing. Our front end is in Next.js though, so we ha
27.
by dyogenez 2y ago
This is true. I’d still need a CDN in front of the actual files to prevent that. That’s a takeaway for me from this feedback.
28.
by dyogenez 2y ago
I hadn't thought of that, but I love the idea! How's that work?
29.
by dyogenez 2y ago
I left off the method that generates the signed URL. It limits the bucket to a specific one per env and blocks some protected folders and file types. I left that out in case someone used it to find an opening to attack.
30.
by dyogenez 2y ago
If this were a business and someone else's money I'd do the same. This is a bootstrapped side project coming out of my own wallet. If money wasn't an issue, I'd probably just allow people to download images for free.

More ›