I’m rewriting Knife City in Rails

Uploaded on May 20, 2023

I’m fed up with my current stack – I’m using a hodgepodge of fucked up and bad modern tools that feel super over-engineered and I’m going back to basics to make a solid, simple, CRUD app.

After years of building stuff in React, I’m fed up. There’s too much infrastructure on top of infrastructure and it’s annoying. For a long time I’ve felt frustrated with what feels like too much over-engineering and popular products being re-created over and over again for no real reason other than the fact that popular oss creators can say that they’re making the next big thing.

Their reply guys can follow these fearless leaders and be the first ones to make some dumb app on top of Remix.run or whatever. I’ve run into so many problems with building my app using ssr and React and I’m tired of it. I want a solid app that has SEO capabilities and I don’t want to re-invent the wheel, or make an app with the sole purpose of learning a new framework, which is how I landed on making Knife City on Next.js in the first place. Recently, the Netlify server functions that power Knife City have been shitting the bed about 1/5 of the time and there’s no good answer to why this is happening.

Rails has been around forever and is a great way to make apps that have great performance, and are simple. I like mvc frameworks and am tired of everything being some async call that takes an unknown amount of time. I want everything to be handled in the controller and that’s that.

I’m learning Ruby and Rails now, I hope to have the new site up within 3 weeks. I’m probably going to rename the site too.