Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Rails Vs PHP

Which is better and what do they do?

3 Answers

Hi Tristan,

I believe what you may have meant to say is Ruby Vs PHP. Rails or Ruby on Rails is a framework for ruby developers.

Both are server side languages, meaning that with whichever one you choose, you will be able to manipulate input from a user and add extra interactivity to your page via the server where your website or app is hosted.

As for which is better, there really is no answer. Everyone has their preferences and every language has their own fanboys/girls that will tell which language is better but it really is up to you to decide. I personally have no experience with Ruby but I hear it has a very easy-to-learn syntax that is geared towards ease of use for the developer vs the computer.

I personally develop in PHP and I love it. It's very quick to learn and deploying a WAMP/MAMP/LAMP server to start working with is as simple as downloading the package and installing the software. From what I have heard, setting up a Ruby environment is a bit more involved and difficult for a beginner.

TL;DR You can do a lot of the same stuff with both these languages, but they are by no means the same. Do the intro course for both and pick the one that makes the most sense to you.

Happy Coding!

What does it mean when people say ruby can't scale?

Honestly, it really depends on what you mean by scale but rather than get into that discussion, here's a great answer I found on stack overflow:

http://stackoverflow.com/questions/1741598/busting-ruby-on-rails-myths

Again, I'm not very knowledgable on Ruby but this response makes a lot of sense to me. Scalability is about growth and you can (theoretically) scale just about anything but there is always going to be a difference in time and money spent.