As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I have seen many people use MySQL, some Postgres and I know I have seen an Oracle adapter somewhere. But really - what should I use just starting out with my first Rails apps?
If you ask such question then probably there is no real difference for you.
Usually a specific DBMS is selected depending on:
Infrastructure limitations (e.g. Heroku provides only Postgres by
default).
Personal preferences (a space of endless holywars).
If you don't have neither first nor second, then choose the most popular, because the most popular means the most supported.
Your first app you should just use sqlite because it's easy and there's no setup required. You'll have enough to worry about with the rails framework, ruby, tdd, etc. Once you get better you should look into postgres. It's what is used by Heroku and most of the rubyists I admire mention their preference for postgres over MySql. I'm sorry but I don't have any specific links for this bias but I've seen it mentioned many times.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I have spent some time familiarizing myself with
rails (ruby),
django...and other things like zope and pylons/pyramid (python),
catalyst (perl)
but often find myself wanting to use
sinatra (ruby)
bottle...or flask...(python)
dancer...(perl)
I'm not entirely sure...when I'm about to start a new project, which I should use.
What should be the deciding factor that makes me switch from a micro framework to something more substantial. Is it just when I would otherwise have too much SQL to write? I think not, because if that were the case I could just use an ORM library/module.
My main issue is a fear of choosing something that other developers would not understand if someone else needed to fix the site at a later point in time. Still I am still not sure what should inform my opinion.
With miсro frameworks you have more freedom in the use of libraries, you can add what you think is right. In large frameworks such as Django and etc already much that is "screwed" and there are certain rules and best practices how best to write certain things.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I've started learning RoR and I really like it - but it feels like it's oriented in one specific way - a very basic MVC model.
Which type of web application might not benefit from using RoR? Are there any signs I can find while planning the architecture?
I don't think there's a specific technical reason not to use RoR - it's fast, clean and can probably do anything PHP does.
The only reasons I can think of are the same consideration as to any other technology : Do you have the right people, is the legacy code (if any) compatible, are you in a market that makes it easy to find RoR people to support the code, and so forth.
There's also a nice Quora thread about this question :
If you have to install your website on a client machine that does not support rails/ruby.
If your code needs to be maintained afterwards by people that do not have rails knowledge.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
i used PHP for my web development, until recently when i started using python framework Django, i enjoy the experience,
but had a chat with my friend and he started saying this and that about me switching to Rail, even with all
my effort trying to explain to him that the are vitually alike he kept echoing rails.
If anyone is actually better than the other, please that i will like to know
Thanks.
It depends on your projects. Rails has a bigger community IMHO, great screencasts. Django has great stuff out of the box. Whereas rails has gems for every task you require and they are always changing (which is good and bad; might be hard to keep up)
Django has an out of the box administration panel and a great templating library.
You can use python egg as far as I know, and other python libraries.
I'd give Django a go first to so as to finish something, but then in the long run using Rails could be of benefit.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
I am interested in learning Ruby/RoR, but it seems to have lost the popularity it had a few short years ago, and from what I've read, few webhosts support it. Is it on its way out?
Still seems to be growing in the U.S., it's just not as hyped as it was. See job stats from indeed
I wouldn't say it's on its way out, it just lost some of the hype--which isn't a bad thing.
I don't think there has ever been a ridiculous amount of hosting support; but there are a few, there's a list of hosts that provide rails support at http://www.rubyonrailswebhost.com/
No.
I find more and more nice little startups that are using it (my favorite recent finds: toggl.com and zencoder.com). There are also many good web hosts, but in my experience the best of them is heroku.com.
If you're interested in learning it, find a local user group. There's always people there willing to share their interest.
I worked for some start-ups and all of them used Ruby on Rails.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
It is said that FastCGI doesn't work well with Ruby on Rails deployment. Why is that? In previous experience, something either works quite well or it might be fundamentally wrong. So if FastCGI is a viable solution, why is it not reliable with RoR?
Does FastCGI work well with most any language / frameworks?
According to DHH himself:
Heck, in the early days, you could
even run Rails as CGI, if you didn't
have a whole lot of load. We used to
do that for development mode as the
entire stack would reload between each
request.
We then moved on to FCGI. That's
actually still a viable platform. We
ran for years on FCGI. But the
platform really hadn't seen active
development for a very long time and
while things worked, they did seem a
bit creaky, and there was too much
gotcha-voodoo that you had to get down
to run it well.