Today I accept that Rails is yesterday’s software

Re:Today I accept that Rails is yesterday’s software by bphogan on Monday May 09, 2016 @02:38PM (#11662059)

You will indeed have to re-implement stuff Rails gives you. But more importantly, you will have to maintain it.

I maintain a large-ish Sinatra app that should've been done with Rails. Update cycles on the gems are a nightmare. It feels cobbled together. it's a "half baked homegrown version of Rails."

Someday I will just move the logic to a new Rails app and be done with it. It was a terrible idea.

* your experience may vary. :)

[ Parent | on HN ]

Re:Today I accept that Rails is yesterday’s software by hkarthik on Monday May 09, 2016 @03:42PM (#11662541)

Any sufficiently complicated Sinatra app contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Rails.

[ Parent | on HN ]

Re:Today I accept that Rails is yesterday’s software by elliotec on Monday May 09, 2016 @03:07PM (#11662283)

My experience was exactly the same. Sinatra is for super tiny things. Rails is for most things.

[ Parent | on HN ]

Re:Today I accept that Rails is yesterday’s software by tchow on Monday May 09, 2016 @03:30PM (#11662461)

What is a large-ish app? Just for comparison's sake?

What makes it large-ish? The number of tables? The number of views?

What is the problem that large-ish apps give that Rails solves?

Genuine questions, I only do small projects and I honestly don't see a huge benefit to using rails, despite having used it before.

[ Parent | on HN ]