Ruby on Rails vs. PHP
leonardteo.com
Ruby on Rails vs. PHP
1–8 of 8 posts
Re: Ruby on Rails vs. PHP
#2I agree. I think that for PHP a huge win would be a big API refactoring, which could be not a big deal, with the right aliasing and deprecation management.
Re: Ruby on Rails vs. PHP
#3This is quite a good write, up, points out when you would want to use one or the other, and not crapping all over PHP just because it isn't a great language.
And interesting that he points out that finding a dev will be way easier in PHP. I had a non developer friend with a start-up application. He had obviously spoken to a number of bioinformatics (he was a wet lab biologist) who had obviously ranted about the benefits of Python. So he got a Django dev. Then got a second stage of funding, to pay for a junior-ish level dev. Except no Python / Django devs (he asked me) were willing to work for the money he had available. Had he gone with PHP, he would have probably managed to continue, despite everyone probably telling him PHP was a crap language.
Re: Ruby on Rails vs. PHP
#4I agree. I think that for PHP a huge win would be a big API refactoring, which could be not a big deal, with the right aliasing and deprecation management.
Considering the usual lack-of-concern of the version of PHP the user is installing/being provided, I could see a significant amount of compatibility problems if PHP came out with a version where weird functions (like strlen() vs str_replace(), how would you resolve the difference in convention here?) were fixed.
Re: Ruby on Rails vs. PHP
#5This is quite a good write, up, points out when you would want to use one or the other, and not crapping all over PHP just because it isn't a great language. And interesting that he points out that finding a dev will be way easier in PHP. I had a non developer friend with a start-up application. He had obviously spoken to a number of bioinformatics (he was a wet lab biologist) who had obviously ranted about the benef…
Finding a developer that is willing to put PHP on their resume on the off chance they'll get a job, and then try and figure it out by scrounging up code on Stack Overflow is not hard.
Finding a good developer is just as hard in any language, since a good developer will be able to go with whatever language you've got.
Re: Ruby on Rails vs. PHP
#6I agree. I think that for PHP a huge win would be a big API refactoring, which could be not a big deal, with the right aliasing and deprecation management.
Considering the usual lack-of-concern of the version of PHP the user is installing/being provided, I could see a significant amount of compatibility problems if PHP came out with a version where weird functions (like strlen() vs str_replace(), how would you resolve the difference in convention here?) were fixed.
With a compatibilty layer, a library which connects the post and the after
Re: Ruby on Rails vs. PHP
#7This is quite a good write, up, points out when you would want to use one or the other, and not crapping all over PHP just because it isn't a great language. And interesting that he points out that finding a dev will be way easier in PHP. I had a non developer friend with a start-up application. He had obviously spoken to a number of bioinformatics (he was a wet lab biologist) who had obviously ranted about the benef…
Finding a developer that is willing to put PHP on their resume on the off chance they'll get a job, and then try and figure it out by scrounging up code on Stack Overflow is not hard. Finding a good developer is just as hard in any language, since a good developer will be able to go with whatever language you've got.
A good developer will be able to go with whatever language you have got. However, (assuming I am a half decent developer) I would avoid jobs in PHP or VB.
Re: Ruby on Rails vs. PHP
#8I agree with a lot of the points he mentioned on this article. PHP for me is much easier for beginners. However, newer platforms may be something experienced developers want to experiment on.