Hacker News new | past | comments | ask | show | jobs | submit login

RoR is a beast, it has its place. The issue we have today is that everything is to fast paced, so fast that people feel the need to follow the latest and greatest, or they will be left behind.

This has (in my opinion) lead to a false sense that if something is not hyped as often, then its not used either.






What do you mean "left behind"? Are you saying people will actually gt "left behind" or just that people will _feel_ like they're left behind?

At this poitn you can find tools that can make demos easier to build or get you further in a hackathon, but Rails embodies "Slow is steady and steady is fast." If you're trying to build something that will stick around and can grow (like a startup outside of the latest VC crazes) then Rails will arguably do better at keeping your tools relevant and supported in the long run. That is, assuming you're building something that needs a steady backend for your application.


> At this point you can find tools that can make demos easier to build or get you further in a hackathon.

I don't understand this at all. ruby on rails is probably peak technology for getting something up an running fast at a hackathon. its a very streamlined experince with a ton of drop in plugins for getting to the product part of the mvp. Maintaining a ruby app is a nightmare overtime. At least it was 5 years ago the last time I worked fulltime in a startup using ruby on rails.

These days I use elixir. its higher performance and reasonably fast to write in but I woudln't say its as productive as ruby on rails if you're competing in a hackathon.


Maintenance nightmares are a product of organizational culture, not any particular framework.

The language encourages metaprogramming, and disencourages typing. This makes maintenance much more complicated when compared to other languages such as Python, typescript or PHP.

Any language can get you a maintenance nightmare, but a lack of types and a monolith will get you there faster.

Nothing in ruby forces you to make it a monolith of course, but the lack of types hurts


> What do you mean "left behind"? Are you saying people will actually get "left behind" or just that people will _feel_ like they're left behind?

Feel.


Heh, maybe us engineers need to be better disciplined about what "greatest" is.

> maybe us engineers

I’ve started qualifying such statements… “you mean a real engineer or just a software developer?


You mean that CSS engineers is not a true title!?

Nah, RoR failed because nobody wants to write code in an untyped, monkey-patch-friendly language anymore.

I don't really know if I would agree on saying that RoR failed, from recent my experiences, it's still a sought after tool for startups.

I do share your opinion on the untyped part, it's a bit of a bummer but there are gems to Ruby that helps with that.

Regarding the monkey patches, it's a concern many have and because of that, there is now a cleaner way of doing it! It's called a refinement. It's like monkey patching but in a more controlled way where you don't affect the global namespace.

https://docs.ruby-lang.org/en/master/syntax/refinements_rdoc...




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: