[inanepenguin]

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.

[cultofmetatron]

> 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.

[sosborn]

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

[Alifatisk]

> 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.