101–110 of 182 posts
People often say Rails is great for startups—perfect for prototyping and moving fast. That’s true, but for me, the real joy comes in maintaining Rails apps. Jumping into the production console, debugging issues, tweaking code on the fly—it’s so satisfying. Yes, it’s risky and you must know what you’re doing. But when done right, support is lightning fast.
Modern React is a "full-stack" framework - with the current recommended implementation being NextJS. If you build on NextJS you will get the entire tailwinds of the industry behind you. Having Cursor write a full-stack app that leverages server components alongside client components is a 10x velocity unlock that you won't get if you bifurcate your codebase (as is the rails model) Typescript is going to be the languag…
But there is LSP support? See: https://shopify.github.io/ruby-lsp/#with-vs-code There's also (the older) solargraph.
This person clearly has no actual rails experience. Every deal breaker he lists has a well established solution in rails.
I use node-ts. Why? I have access to every library I will need from any provider or for any task like phone number validation. Node is fast enough, easy to develop, deploy, and scale. Anything that is slow can be ported to Go. It is easy to find solutions to my immediate problems using LLMs. I’m just using express and my data layer consists of neo4j and qdrant. All code is single responsibility and I use layered arch…
Are you saying that’s because RoR was used? Doesn’t seem plausible. Messy bad code is the fault of the programmer, not the language/framework
The best thing about Rails is its strong, opinionated defaults for building web applications. It handles HTTP request routing, data marshalling, SQL interactions, authentication/authorization, database migrations, job processing, and more. That means you can focus on business logic instead of wiring up the basics.
Rails isn’t as fast or lightweight as Go, but they solve different problems. For most web apps, the bottleneck is I/O, not CPU. Rails optimizes for developer productivity, not raw performance, and that tradeoff is often worth it, especially when speed of iteration matters more than squeezing out every last cycle.
People often say Rails is great for startups—perfect for prototyping and moving fast. That’s true, but for me, the real joy comes in maintaining Rails apps. Jumping into the production console, debugging issues, tweaking code on the fly—it’s so satisfying. Yes, it’s risky and you must know what you’re doing. But when done right, support is lightning fast.
Changing production code on the fly? So testing/qa is done on production? Uh, no thank you.
I use node-ts. Why? I have access to every library I will need from any provider or for any task like phone number validation. Node is fast enough, easy to develop, deploy, and scale. Anything that is slow can be ported to Go. It is easy to find solutions to my immediate problems using LLMs. I’m just using express and my data layer consists of neo4j and qdrant. All code is single responsibility and I use layered arch…
And I’m a mainly JS dev. Node is extremely easy to f up, so is the frontend. And with all the generated code today… it’s gonna get only worse.
While Ruby on Rails still offers strong productivity benefits, the hiring landscape has shifted significantly, particularly here in Australia.
Experienced Ruby on Rails developers are increasingly scarce, as many have moved on to JavaScript, Python, or, as you say, Go. The talent pool is also saturated with AI-generated resumes that don’t translate to actual skills when you interview them.
If you struggle to hire Rails engineers now, it will only get harder as fewer new developers adopt the framework, and maintenance will become a challenge as the ecosystem shrinks.
Maybe it's a much larger pool elsewhere or if you can accept 100% remote.
Earlier quoted context omitted.
I definitely recommend using Ruby, and Rails. The Jason Fried and David Hansson Musk/Fascist vibes are real and are a problem. Most of the people in the Ruby community recognize that problem and are taking steps to mitigate that issue. Most of the core Rails committers don't work for 37 signals, and it's not really a thing made just by them. Definitely use Rails to start a new project. The real hero here is Ruby and…
>The Jason Fried and David Hansson Musk/Fascist vibes are real and are a problem. What do you mean by this? Where have Jason Fried or David Hansson supported fascism? Your account is ten years old and this is the first comment you've ever made.
I mean that they give off Fascist vibes, and that it's a problem. Adoration for and support of fascist people and regimes are implicit support of fascism. Not explicit.
Go read their blogs, I'm sure you'll find lots of examples.
Earlier quoted context omitted.
Is it boring technology? I'm actually reluctant to pick up Rails because it had always been sold by the Basecamp cult and Jason Fried gives off Musk vibes. Many opinionated frameworks are also less reliable because of the layers of abstraction, so I'd also associate opinionated framework = sexy and temporary. I've never actually used Rails in production, just did some tutorial, so I'm probably wrong about this.
>I'm actually reluctant to pick up Rails because it had always been sold by the Basecamp cult and Jason Fried gives off Musk vibes. Why? What "Musk vibes" have they given off?