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 starting a website and am wondering if I should go with PHP, a php framework, or ruby on rails? I want to make a website fast, easiest and without a big learning curve. I already know a little bit of php and a little ruby on rails...But which would be best?
OK so to clarify more on the topic of what my site will be, It's basically a Classified Ads website that needs to have a user login, ability to post classifieds, and categorizing, and basically anything else a classified website has.
I would put my vote in for Rails. It's easy to get started building a website that requires persistence in a database, and there are many websites that host the framework. I agree with #Squeegy that PHP is great for sprinkling dynamic content into an otherwise static page, but it sounds to me that you want something more involved, so I would go with Rails.
Start with anything you know better.
PHP is great for sprinkling bits of dynamic content into a website. Given your requirements "fast, easiest and without a big learning curve" I think PHP would be ideal.
Now a large and more complex site, that would be much better suited to a framework. But with any framework also comes steep learning curve.
Codeigniter.com, try it out, it rocks.
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 10 years ago.
I'm a college student trying to make a web community with friends. Although we are not experienced developers by any means, we have taken courses on JAVA and some web programming languages (PHP, JAVASCRIPT, CSS, HTML).
At this point, we need to decide on a web framework and begin learning. I have narrowed down my list to Ruby on Rails and Codeigniter, but I am really not sure why I should pick one over the other.
Thanks in advance.
Pick the one you want to learn and go with it.
I will personally recommend Rails because:
it teaches you a lot of best practices if you do things the Rails Way™
Ruby is a fun, easy-to-learn, expressive language
the community is really big, enthusiastic, and very helpful
there's great books and tutorials available all over the internet
There is nothing like the good framework. It highly depends on, in no particular order :
your skills
your tastes (Yes, it does matter a lot)
your willingness to learn
technical constraints. Your hosting company may support only Ruby or only PHP
...
I personally had the occasion to develop with CodeIgniter and I pretty much enjoyed it. It is light, well documented and leaves you with a lot of freedom.
I also have a good friend for whom Ruby On Rails is the only framework deserving the name of "framework".
If your project is ambitious, a good idea to make your point could be to make a trivial application like a TODO list with both framework and then pick the one that fits your need.
Hope this helps.
If there is no time constraint (as you need to learn both ruby lang and rails framework) and want to know the best practices, i would recommend RubyonRails.
If you have time constraint, then go ahead with Codeigniter. It is easy to learn and well documented.
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 10 years ago.
Am thinking about building a social networking site,that can function more like an application then a site,thus giving it better performance and user interface.
what am stuck up with here is which would be the best framework to try this out?
GWT-i have some experience(about 2 years) with Java and it looks easy but the forum appears dead.
Ruby on Rails- i visited the website today,went through a few tutorials and it looks easy to learn,but i never programmed on this 1 before.
Grails - i have heard that this is a very god framework and based on java,but i've never personally tried it.
What would you think would be the right choice?
it would be cool if you consider factors like performance,scalability and the widgets already available.I don't really care about the development time...i've got more than 2months!
Especially with a Java background, Grails would be a good choice. Grails is built on top of Spring and Hibernate, but makes using them much easier. No painful editing of XML config files.
Although, I'd make sure you evaluate using Ning and the existing open source projects before you bother building another one from scratch.
I'm not sure what you mean by "more like an application then a site". If what you mean is give the app a desktop application feel, then I think GWT fits more. Though if you want to have something really fast, (half the development time that you'd use to develop it in GWT), then I'd recommend rails. I haven't tried Grails before but it seems neat.
The best for you to use is ruby on rails if it about performance,scalability and the widgets
then you have no problem at all. It also has lots of gems/plugins that can help you so much
Read this book Grails in action.
It shows you how to make a social networking site using grails.
It uses an old version of Grails but you can adapt it.
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.
What are the WordPress alternatives for Ruby on Rails? How do they compare to WordPress?
Refinery looks really simple but I don't have an in depth comparison to WordPress. Looks like it has a lot less features but likely easier to maintain and extend upon. It's pretty standard to write really crappy code in the WordPress community.
I've been using WordPress more or less against my will for about two four years now (since I started using other frameworks (I've started to really love WP again)). I think there is no "good Rails alternative". Of course there are a lot of blog engines but none have as many plugins available or are as well known with clients. Let's be honest, WP has a fantastic front-end, clients seem to like that. The reason "we developers" look for Rails alternatives is obviously because Rails developer aren't comfortable with WP. But there's no platform out there that has the same out-of-the-box completeness and user friendliness as WP. For blog-like purposes that is of course.
Publify can be a answer, but I'm not able to compare with WordPress.
You may want to look into Wordscript ; it includes API's written in Ruby and PHP that connects to existing WordPress databases and returns json structures (made from generated SQL).
Useful if you want to keep full administrative features of WordPress, and have a somewhat simple WordPress site. Neither version requires WordPress to be installed locally, but you can't really do anything administrative with the api or comments/custom fields (yet). Also the API is much faster and consumes a fraction of the resources WordPress would.