Hacker News Reader

Comment by xyzzy4747 | Hacker News Reader

I don't know why anyone would want to code with a language that isn't statically type safe at compile time in this day and age.

View on HN

Might be worth spending 30 minutes watching a video of what you can build with Rails in that amount of time instead of smugly dismissing it.

There’s a great example on the home page here: https://rubyonrails.org/

I've used it before, but Next.js with TypeScript is much superior in many different ways.

Honest question: Where do you deploy? What do you use for queues? Database? It's impossible to beat React for component libraries but, lemme tell you, I've struggled to be productive with Next when compared to Rails.

I don't know if I'd admit that publicly, without first reading about it and trying to understand why things like RoR and Python have huge, loyal user bases.

Doesn’t tools like Sorbet and RBS help?

Why use a 3rd party add-on solution instead of using something better in the first place?

You mean like Typescript, an add-on that transpiles to Javascript?

I'm sure they meant an actual statically typed language. I agree that dynamic languages are fun and productive ... until the codebase becomes big and complex, and then not knowing what shape any data is quickly becomes a nightmare to understand and debug.

> not knowing what shape any data is quickly becomes a nightmare to understand and debug

I remember when I experienced exactly this, it kind of flipped switch in my head which made me love static typing.

RBS comes by default with Ruby, Sorbet is 3rd party.

That is why I use Laravel btw

Reply on news.ycombinator.com