Okay, for what it’s worth:
All frameworks have a big limitation – they work so long as you do things “their way”. If you go, well, “off the rails”, all bets are off, and you are probably in a pretty painful place. This is definitely true of Rails. But. Somehow it is less true than it should be.
(For example I recently looked into customising Rails’ scaffolding process so that I could generate basic CRUD maintenance screens with the same look and feel as we use here with Sinatra. There was some documentation, and where it was inadequate, generally the first thing I tried worked. Given the above, this is nothing short of miraculous, and the Rails developers should be applauded.)
In my opinion Rails is optimised for *development*. It will let you get something up and working and even deployed in a ridiculously short time. That is an amazing thing. But if you are looking to deploy permanently for a lot of users or with limited resources, you had better know what you are doing. And I wonder, when you know enough, what the chances are that you will then realise you are better off using something else…
One last thing. You should be aware that Rails has a learning curve – you need to know “Rails” not just Ruby -- and is a rapidly changing product. Those two things taken together might be problematic.
···
From: ruby-talk [mailto:ruby-talk-bounces@ruby-lang.org] On Behalf Of A Berger
Sent: 02 August 2016 2:47 pm
To: Ruby-Talk Mailingliste
Subject: Rails
Hi
Sure thats not a Rails-Forum,
but there you'll get no objective answers 
For me Rails looks very complicated:
If wanting one thing, I have to change code at 100 different sources.
Were earlier releases less confusing?
If adding a new relation one change (name+relation-types) should suffice, most other necessary changes could be derived from that!
And I never know what Rails does exactly (maybe I could look at the Rails-sources, but thats too much...
Mapping Url to methods could be done with few lines, besides I would prefer only one level (mapping file) - (fullurl) /regex/ matching, and the other way round (method to url).
What do you think?
Isnt it very (too?) big? Do you really save much time using it?
Can you compare it to other Frameworks?
How much time will I need to use it productive? - for (over)simplification say Ruby expert, Rails nobie.
Maybe as nowbie (newbie/nilbie) I don't have the right insight yet!
Thx Berg
Click here to view Company Information and Confidentiality Notice.<http://www.jameshall.co.uk/index.php/small-print/email-disclaimer>
