Why would anyone use ROR over PHP?
- Thread starter lcver
- Start date
No but I've run ROR apps and they're all slow. I researched it and dev time is slightly quicker but takes a huge hit to performance/scalability.
Also, having the ability to compile PHP into C++ with one of the many available open source programs makes the scalability insane.
Also, having the ability to compile PHP into C++ with one of the many available open source programs makes the scalability insane.
Without any context to what you're trying to achieve this is a pointless discussion.
If your main aim is insane scalability then your insanely scalable language will be the best.
If I don't care about insane scalability, a language or framework with more relevant features would be better
If my main criteria was a language that contained only the letters r, u, b and y then ruby would dick all over your insanely scalable PHP
(Pretty sure I'm posting in a troll thread)
If your main aim is insane scalability then your insanely scalable language will be the best.
If I don't care about insane scalability, a language or framework with more relevant features would be better
If my main criteria was a language that contained only the letters r, u, b and y then ruby would dick all over your insanely scalable PHP
(Pretty sure I'm posting in a troll thread)
Why would anyone choose PHP over ROR? You know this could literally go on forever, right?
It all ends up with two things: the comfort of the programmer doing it, and what the intended use is.
(O_o)
H̨̼̩͐̑͆̀̚&
<tinfoil>
because PHP is made by the CIA to brainwash everyone by setting the computer monitor to flicker at 222 mHZ which dumbs your mind down via floride in the water.
because PHP is made by the CIA to brainwash everyone by setting the computer monitor to flicker at 222 mHZ which dumbs your mind down via floride in the water.
not knowing what your doing makes this question unanswerable.
its like saying why would you chose a mallet over a hammer? mallets and hammers can pretty much do each other jobs, but each one is specialized and better suited for certain jobs.
I.E., im not building a staircase with a mallet, but Im not using a hammer to push/wedge into place something made out of bronze.
its like saying why would you chose a mallet over a hammer? mallets and hammers can pretty much do each other jobs, but each one is specialized and better suited for certain jobs.
I.E., im not building a staircase with a mallet, but Im not using a hammer to push/wedge into place something made out of bronze.
You have no idea what you're talking about.
Rails is used by people who prefer to launch profitable products rather than engage in theoretical circlejerks over which language/framework/library is faster.
If I weren't so busy, I'd challenge you to two races simultaneously: I guarantee I can build a Rails app faster than you can build a PHP app, and I can make my Rails app scale better than your PHP app
^^ realistically here Darrin, wouldn't that be more of a function of how good of a coder you are in X Language?
i.e., I can write a PHP app 30x faster then I can a Ruby/rails app because I have been coding in PHP for 10 years if not more and rails for like 3 months.
I also believe scale is a function of how good of a coder you are too.
I won't debate if you are equally good at both languages though, which one will win as we all know that question ( queue up Mattseh.. )
i.e., I can write a PHP app 30x faster then I can a Ruby/rails app because I have been coding in PHP for 10 years if not more and rails for like 3 months.
I also believe scale is a function of how good of a coder you are too.
I won't debate if you are equally good at both languages though, which one will win as we all know that question ( queue up Mattseh.. )
with the gem ecosystem and generator based nature of Rails, most apps can be spun up in a pretty trivial amount of time. But skill of coder definitely plays in to it absolutely.
Honestly, someone like Lee is best suited for weighing in on such a debate. I've built sites on Rails and CodeIgniter and the only real advantage a PHP framework has over Rails is ease of deployment (you could run a CI app on fucking hostgator if you wanted, Rails requires full ssh access and sudo access, etc). But from a coding perspective, never in a million years would I build anything in PHP again...Rails is just too good once you learn how it works.
Huh?
Yes, because we all know:
Code:
$db = new DB();
$result = $db->select("col1,col2")->from($table)->where(array('col3' => '43'))->order('id')->limit(30);Is oh so much more efficient than:
Code:
$result = mysql_query("SELECT col1,col2 FROM $table WHERE col3 = '43' ORDER BY id LIMIT 0,30");
Indeed, the former makes me want to kill myself. It's bad, and anyone that uses it should feel bad.
Using a PHP ORM to show off the utility of an ORM is like talking about great driving experiences by using a KIA as an example
Because there are serious people doing development time research who have determined that Ruby on Rails is a waste of time apparently. Also, there are a bunch of hacky coders weighing on in the topic.