5 ms·

And that is why I won't be learning ruby any time soon. I think I'll stick to PHP.

by shane-armstrong 14y ago

saturnflyer 14y ago
Really!? So PHP simplifies all this for you, huh?
- shane-armstrong 14y ago
  My experience with PHP has not been as terrible as most rails users make it out to be. Once I learned the PHP syntax I got flying with it, I didn't have a single problem. I just don't see the point in ditching PHP now to learn ruby just because it has become the latest online fad, better to stick with what I know until I develop serious problems with PHP which I believe only changing languages could solve.
  - rfelix2121 14y ago
    That kind of thinking is the exact type that will lead you to wondering why you can't find a programming job when you're 40.
  - xyzzyb 14y ago
    Always be learning. Don't learn Rails to make a career out of it (although that may end up happening!), learn Rails to expand your mental models. And don't just learn Rails! Learn Django. Learn Sinata. Learn Erlang-Web or Nitrogen. Learn Smalltalk. Learn TeX. Learn JavaScript (actual JavaScript). Learn Node.js. Learn Meteor. Learning a language doesn't mean "ditching" anything. You're adding! And one more thing: Ruby[sic] is far from the latest online fad. That would be JavaScript and Node. Rails was the latest online fad back in 2007.
Pewpewarrows 14y ago
To be fair, you need to know the entire left-hand side of that graphic with PHP. The bottom-right quadrant is stuff you _should_ be doing (formalized methodology, version control, and testing). And the top-right quadrant is language-specific, in that you can replace it all with PHP and your PHP framework of choice (if necessary). How exactly does PHP make it easier again?
- shane-armstrong 14y ago
  Because I already know PHP. The experience would be different for someone new to programming but I have no reason to learn Ruby at the moment.
mrsteveman1 14y ago
Do you use a full featured PHP framework akin to Rails?

And that is why I won't be learning ruby any time soon. I think I'll stick to PHP.

saturnflyer 14y ago

Really!? So PHP simplifies all this for you, huh?

shane-armstrong 14y ago
My experience with PHP has not been as terrible as most rails users make it out to be. Once I learned the PHP syntax I got flying with it, I didn't have a single problem. I just don't see the point in ditching PHP now to learn ruby just because it has become the latest online fad, better to stick with what I know until I develop serious problems with PHP which I believe only changing languages could solve.
- rfelix2121 14y ago
  That kind of thinking is the exact type that will lead you to wondering why you can't find a programming job when you're 40.
- xyzzyb 14y ago
  Always be learning. Don't learn Rails to make a career out of it (although that may end up happening!), learn Rails to expand your mental models. And don't just learn Rails! Learn Django. Learn Sinata. Learn Erlang-Web or Nitrogen. Learn Smalltalk. Learn TeX. Learn JavaScript (actual JavaScript). Learn Node.js. Learn Meteor. Learning a language doesn't mean "ditching" anything. You're adding! And one more thing: Ruby[sic] is far from the latest online fad. That would be JavaScript and Node. Rails was the latest online fad back in 2007.

Pewpewarrows 14y ago

To be fair, you need to know the entire left-hand side of that graphic with PHP. The bottom-right quadrant is stuff you _should_ be doing (formalized methodology, version control, and testing). And the top-right quadrant is language-specific, in that you can replace it all with PHP and your PHP framework of choice (if necessary). How exactly does PHP make it easier again?

shane-armstrong 14y ago
Because I already know PHP. The experience would be different for someone new to programming but I have no reason to learn Ruby at the moment.

mrsteveman1 14y ago

Do you use a full featured PHP framework akin to Rails?