Ruby or PHP??
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
I believe PHP is more widely used, and therefore could be beneficial when compared. But there's nothing wrong in learning both. :)
"Real men drive manual transmission" - Rajesh.
-
I believe PHP is more widely used, and therefore could be beneficial when compared. But there's nothing wrong in learning both. :)
"Real men drive manual transmission" - Rajesh.
Thanks for your comment. Which one will be good to start first?
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Already I'm bit confused which one would be better to start first and you're suggesting another one (Python) :rolleyes: Anyhow thanks for your suggestion.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Thanks for your comment. Which one will be good to start first?
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
There's no such "good to start first" thing, but learning PHP may be more beneficial. Both are easy to learn though.
"Real men drive manual transmission" - Rajesh.
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
I'd start with Ruby and take a look at the excellent articles from Marc Clifton here no Code Project.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
There's no such "good to start first" thing, but learning PHP may be more beneficial. Both are easy to learn though.
"Real men drive manual transmission" - Rajesh.
Okay, thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
I'd start with Ruby and take a look at the excellent articles from Marc Clifton here no Code Project.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easierThanks Pete.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
Any special reason why those two? It all depends on your environment and free time. There are new things coming up every day and not enough time to learn them all. So for me to choose to actually learn one is a matter of thinking if I'll ever use them, otherwise I'll just read about it a bit, acquire the basics and walk away.
-
Any special reason why those two? It all depends on your environment and free time. There are new things coming up every day and not enough time to learn them all. So for me to choose to actually learn one is a matter of thinking if I'll ever use them, otherwise I'll just read about it a bit, acquire the basics and walk away.
Great explanation :thumbsup:
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
I have a question, why did you choose these 2 languages? What I see nowadays is that you have to choose the technology based on the direction you want to go towards. So, if you would like to go towards web development, both of these languages are OK to learn, but if you would like to make mobile apps, then these are not for you. If I would need to learn a new language I would choose JavaScript. In the past couple of years the support for JavaScript based technologies has increased a lot and now, you can create back-end and front-end using just JavaScript. I really think this is cool. In the old days there were back-end developers and front-end developers, each had their own languages but this tendency is really gone now...
-
I have a question, why did you choose these 2 languages? What I see nowadays is that you have to choose the technology based on the direction you want to go towards. So, if you would like to go towards web development, both of these languages are OK to learn, but if you would like to make mobile apps, then these are not for you. If I would need to learn a new language I would choose JavaScript. In the past couple of years the support for JavaScript based technologies has increased a lot and now, you can create back-end and front-end using just JavaScript. I really think this is cool. In the old days there were back-end developers and front-end developers, each had their own languages but this tendency is really gone now...
Quote:
I have a question, why did you choose these 2 languages?
I'm into web development through .Net. Now want to have some hands on on Ruby/Php.
Quote:
If I would need to learn a new language I would choose JavaScript.
Agreed. And thanks a lot for mentioning about Javascript.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Quote:
I have a question, why did you choose these 2 languages?
I'm into web development through .Net. Now want to have some hands on on Ruby/Php.
Quote:
If I would need to learn a new language I would choose JavaScript.
Agreed. And thanks a lot for mentioning about Javascript.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
PHP is primarily used for web development. Ruby is a scripting language (along with Bash, Perl and Python). These language can be used for web development but can be used for a variety of other things. This all said, you should be able to pick up PHP in a matter of a few weeks. Ruby will take a few more weeks with Rails / Sinatra taking an addition 1-2 weeks after that.
-
I'm going to start learning these languages, which one would be better to learn first among these two (Ruby & Php)? May be it is matter of self choice to choose a language but just want to make sure if it makes any difference. Thanks.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
Allow me to interject a little personal philosophy. I’ve worked in fifteen languages, not counting “shells” as languages or non-Turing complete things that are called languages (e.g. XML, HTML). You can only be “really good” in maybe five to seven of them, and a good number of those fifteen I hope to never lay eyes on again. Their entry to my skillset came from one of four sources: personal choice, academic dictate, project dictate and vendor dictate. Academic dictates are those languages you have to learn in college. Project dictates are those languages that you are forced to learn by the projects you work on. Vendor dictates are languages you have to learn to work with a vendor’s product; for instance if you work in Oracle databases you’ll need to know SQL and probably PL/SQL. The languages that are dictated to you are almost always unsatisfactory intellectually, because teams are intellectually diverse, and tools need to be chosen on projects for the least common denominator, or to put it more bluntly, the lowest IQ, the least motivated to learn new things, the least capable of grasping abstract concepts. Therefore my recommendation for personal choices is to choose languages that you are unlikely to have dictated to you by any other means. Go for the languages that most pique your interest. It is preferable to learn languages that help you expand your problem solving skills. Working in imperative languages? Try a functional language so you can broaden your approaches to working on problems. Working in compiled languages? Try scripting languages. The core idea is to broaden your range and breadth of knowledge compared to your colleagues. The most interesting languages I know have all been personal choices. I’ve practically never had an interesting language dictated to me by academics, projects or vendors. Of course I’ve subsequently been on projects using some of those personally interesting languages, so there is naturally some intersection between personal choices and project work. So the answer to Ruby or PHP is, which one interests YOU the most, period. Forget about what’s more marketable or whatever other criteria you might have, or what language Joe Blow thinks you should learn instead. It’s not like your brain can’t hold more than one new language, especially if you get in the habit of learning new languages every year or two (or three at the worst).
-
Allow me to interject a little personal philosophy. I’ve worked in fifteen languages, not counting “shells” as languages or non-Turing complete things that are called languages (e.g. XML, HTML). You can only be “really good” in maybe five to seven of them, and a good number of those fifteen I hope to never lay eyes on again. Their entry to my skillset came from one of four sources: personal choice, academic dictate, project dictate and vendor dictate. Academic dictates are those languages you have to learn in college. Project dictates are those languages that you are forced to learn by the projects you work on. Vendor dictates are languages you have to learn to work with a vendor’s product; for instance if you work in Oracle databases you’ll need to know SQL and probably PL/SQL. The languages that are dictated to you are almost always unsatisfactory intellectually, because teams are intellectually diverse, and tools need to be chosen on projects for the least common denominator, or to put it more bluntly, the lowest IQ, the least motivated to learn new things, the least capable of grasping abstract concepts. Therefore my recommendation for personal choices is to choose languages that you are unlikely to have dictated to you by any other means. Go for the languages that most pique your interest. It is preferable to learn languages that help you expand your problem solving skills. Working in imperative languages? Try a functional language so you can broaden your approaches to working on problems. Working in compiled languages? Try scripting languages. The core idea is to broaden your range and breadth of knowledge compared to your colleagues. The most interesting languages I know have all been personal choices. I’ve practically never had an interesting language dictated to me by academics, projects or vendors. Of course I’ve subsequently been on projects using some of those personally interesting languages, so there is naturally some intersection between personal choices and project work. So the answer to Ruby or PHP is, which one interests YOU the most, period. Forget about what’s more marketable or whatever other criteria you might have, or what language Joe Blow thinks you should learn instead. It’s not like your brain can’t hold more than one new language, especially if you get in the habit of learning new languages every year or two (or three at the worst).
-
Allow me to interject a little personal philosophy. I’ve worked in fifteen languages, not counting “shells” as languages or non-Turing complete things that are called languages (e.g. XML, HTML). You can only be “really good” in maybe five to seven of them, and a good number of those fifteen I hope to never lay eyes on again. Their entry to my skillset came from one of four sources: personal choice, academic dictate, project dictate and vendor dictate. Academic dictates are those languages you have to learn in college. Project dictates are those languages that you are forced to learn by the projects you work on. Vendor dictates are languages you have to learn to work with a vendor’s product; for instance if you work in Oracle databases you’ll need to know SQL and probably PL/SQL. The languages that are dictated to you are almost always unsatisfactory intellectually, because teams are intellectually diverse, and tools need to be chosen on projects for the least common denominator, or to put it more bluntly, the lowest IQ, the least motivated to learn new things, the least capable of grasping abstract concepts. Therefore my recommendation for personal choices is to choose languages that you are unlikely to have dictated to you by any other means. Go for the languages that most pique your interest. It is preferable to learn languages that help you expand your problem solving skills. Working in imperative languages? Try a functional language so you can broaden your approaches to working on problems. Working in compiled languages? Try scripting languages. The core idea is to broaden your range and breadth of knowledge compared to your colleagues. The most interesting languages I know have all been personal choices. I’ve practically never had an interesting language dictated to me by academics, projects or vendors. Of course I’ve subsequently been on projects using some of those personally interesting languages, so there is naturally some intersection between personal choices and project work. So the answer to Ruby or PHP is, which one interests YOU the most, period. Forget about what’s more marketable or whatever other criteria you might have, or what language Joe Blow thinks you should learn instead. It’s not like your brain can’t hold more than one new language, especially if you get in the habit of learning new languages every year or two (or three at the worst).
Thanks. It was very interesting to read your comment :thumbsup:
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
-
Quote:
I have a question, why did you choose these 2 languages?
I'm into web development through .Net. Now want to have some hands on on Ruby/Php.
Quote:
If I would need to learn a new language I would choose JavaScript.
Agreed. And thanks a lot for mentioning about Javascript.
My Reading-o-Meter
Previous -> Read "CLR via C#" by Jeffrey Richter. Current -> Exploring WCF thru Apress' "Pro WCF" by Chris Peiris and Dennis Mulder. Next -> Need to read "The Art of Computer Programming" by Donald E. Knuth.
I'm also a .NET guy, but nowadays I see everyone shifting towards platform dependent technologies. For example I really like to use/code/hack under linux, but the .NET development is done under linux, so I have both OSes available. I know some PHP, but I'm not an expert. It would be interesting to learn Ruby, but just for fun and hacking around.
-
@Reese - Very well stated, and I agree with your philosophy :) Out of curiosity, what have you found to be the most interesting languages?
Good question! I guess it depends mostly on what I didn't know at the time. My first self-chosen language to learn was C, because it wasn't part of the curriculum in my school and inarguably a very important language to know at the time, and yes, I found a lot of the low-level stuff you could do with it quite interesting. Of course I also learned C++ and liked it very much as well, but frankly I haven't kept up with C++ as it has gotten more convoluted feature rich. The very name of the most recent C++ is so complex I can't remember it for a certainty off-hand. Lisp was a standout, because it is such a departure from the languages I normally use that I found it very interesting to work with. It was sort of like exercise, making my brain "bend" in a way it didn't normally "bend." Most of my Lisp code hit the recycle bin, but I now use Emacs in part because of the ability to add a little text manipulation in Lisp when I need to. I have a pocketful of Lisp utilities I've written for Emacs that come in amazingly handy when I program for batch processing (which has been my bread and butter on project after project for the past 16 years). The mixture of OOP and functional features like lambdas and so on made me enthusiastic to learn Python, and Python has served me extremely well and very frequently--it is one of the best languages in existence, in my opinion. The frustration with it is the incredibly slow adoption of Python 3, and the incompatibility of 2 and 3 code. That may be the death blow to an otherwise excellent language. Not every experiment ends in success. For some reason I can't work in Prolog--my brain apparently doesn't bend that way; either that or I didn't pursue it long enough to have the Eureka moment. I guess I couldn't get my mind around describing my problem and letting the computer solve it. The most recent one I learned by my own choice was Scala; it's quite good but the documentation all tends to be trying to sell you on the idea of Scala rather than answering your questions, not totally surprising since the source is academia. It's a more pleasant-to-use alternative for almost anything you'd do in Java. Given that I found Lisp so interesting, I probably should learn Clojure, and I have a bookmark for that, but more bookmarks than enthusiasm, I guess, and how many JVM languages or Lisp dialects does one really need? If I worked routinely in .NET, I would look at F# in detail. Ironically, to the original question, I chose to look at PHP over