Why would anyone use ROR over PHP?

oh man... people still use Ruby???

I kid. To each his own, there are advantages and limitations of all programming languages, and their strengths are interdependent on the skill set of the programmer, the environment, and end goal. 3 weeks ago I was all gun-ho on Perl, recently I've been killing it with jQuery, javascript, even dabbled in some php and C++ again. It all depends... But seriously...

1E8lP.jpg
 


Real coder always prefer doing things in LISP.

But then something strange happens:
They all change at the design phase, after the design document, in the last minute to a different language.
No special reason, they justed missed lisp because the compiler was busy or the handbook was forgotten in the garage. Its strange.

But original they want to do it in LISP.
 
Here you'll find developers comfortable with their own skills who build apps to monetize them. If you spend 5 years to code with PHP you want to monetize your skills at maximum level.
Your question belongs to philosophy.
Choices are based on needs not on philosophy
I myself prefer syntax of Python over PHP, I just love Python clearness but in this moment the world is LAMP-based and I deal with it.
I have started to use Ruby and ROR because I needed to use a CSS pre-processor like SASS/COMPASS, the only way was to install Ruby, now I use and love both SASS and Ruby, there is nothing sweet like Gems in the programming languages world.
8-10 years ago JavaScript was one of the most underrated language in the world, maybe within 5 years we'll use JavaScript for everything: server-side, client-side, desktop and mobile.
 
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

Oh yea... Bet I can knock out one in QuickBasic quicker than that and have tighter code. Oh Snap !! DOS is dead.... Never mind. :)

Moral of the story. Just because your dick is bigger than mine, doesn't mean you get more pussy than me. :)

Carry on....
 
Oh yea... Bet I can knock out one in QuickBasic quicker than that and have tighter code. Oh Snap !! DOS is dead.... Never mind. :)

Moral of the story. Just because your dick is bigger than mine, doesn't mean you get more pussy than me. :)

Carry on....

I fucking love QuickBasic
 
Code:
Model.query.filter_by(Model.c=43).order_by(Model.id)[:30]
Didn't check for correctness but you get the idea.

Don't repeat yourself - Wikipedia, the free encyclopedia - It's like the red pill.

Also, being able to generate queries on the fly in response to varying conditions without fucking around with string manipulation is fantastic.

Code:
list($e, $row) = db_cget($table, '43', 'c');

Hah! Mine's smaller. :) j/k, like it hardly matters.

I'll stick with SQL statements though, because I think getting away from them would be a bad habit to get into, and would hurt the performance of your app. If I just need a simple row and know the exact ID#, then I have functions like above, but for the most part, will stick with SQL statements.


I was running LAMP installs back when the P stood for Perl, not that fag noob php bullshit.

Ditto. Those were actually pretty good days to be a developer, eh? I remember being all pissed off when the mainstream switched over to PHP, because that meant I had to too. Hated PHP at first too.
 
Good reading on LISP:

Beating the Averages

During the years we worked on Viaweb I read a lot of job descriptions. A new competitor seemed to emerge out of the woodwork every month or so. The first thing I would do, after checking to see if they had a live online demo, was look at their job listings. After a couple years of this I could tell which companies to worry about and which not to. The more of an IT flavor the job descriptions had, the less dangerous the company was. The safest kind were the ones that wanted Oracle experience. You never had to worry about those. You were also safe if they said they wanted C++ or Java developers. If they wanted Perl or Python programmers, that would be a bit frightening-- that's starting to sound like a company where the technical side, at least, is run by real hackers. If I had ever seen a job posting looking for Lisp hackers, I would have been really worried.

Real coder always prefer doing things in LISP.

But then something strange happens:
They all change at the design phase, after the design document, in the last minute to a different language.
No special reason, they justed missed lisp because the compiler was busy or the handbook was forgotten in the garage. Its strange.

But original they want to do it in LISP.
 
Also, having the ability to compile PHP into C++ with one of the many available open source programs makes the scalability insane.

When people think that code is the only thing that needs to scale, they have bigger problems than what language to use.
 
RoR has a community focused on improving development practices. Whether they are right or wrong, this is an asset.

RoR has many decisions that are made for you that you can change if you want. Given you can make a finite number of good decisions in a day, this is useful.

PHP is a straight up clustercuss of different opinions on what makes for good software. Low barrier of entry which is nice for an amateur. Lots of choices which is good for neurotic developers. Ease of finding a huge quantity of developers of unknown quality which is good for managers.

So they both have benefits depending on who you are.
 
I6GSf.gif


Seriously though, when programming, there are a million different technologies and methodologies, and personal coding preferences are a dime a dozen. I rarely see an argument against a given language or framework that can't be shot down by someone who knows what they're doing in that environment. Coding preferences vary wildly from one person to the next and while all languages and frameworks tend to have their own pros and cons, in the end it comes to the general skill of the developer as to the quality and efficiency of the product produced. If you think your way is the only valid way, or the best way, you probably just haven't been far enough around the block.
 
When people think that code is the only thing that needs to scale, they have bigger problems than what language to use.

There are obviously several other things that come into play when scaling, that's a no-brainer. We're talking about the language here, not the programmer, hardware, etc... My point being RoR is already heavier than PHP right off the bat.
 
Also, do you RoR advocates have anything to say about the language itself? The only arguments so far have been about the developer which furthers my suspicions of them all being hipsters with a superiority complex. Try to convert me. :)
 
Also, do you RoR advocates have anything to say about the language itself? The only arguments so far have been about the developer which furthers my suspicions of them all being hipsters with a superiority complex. Try to convert me. :)

Why do you assume that anyone cares (or has the actual time to bother) about trying to convert you? If you want some useful information, start here. There are plenty of links to help you come to your own conclusions.

Ultimately though, you won't know for yourself until you've tried writing a few projects in each language.
 
I don't know, I played around with Ruby before, and immediately felt boxed in. Same as I did when I went from Perl to PHP, but even worse.

When I develop something, I want a clean canvass to start with. I don't like having a bunch of restrictions and methodologies forced upon me.
 
Also, do you RoR advocates have anything to say about the language itself? The only arguments so far have been about the developer which furthers my suspicions of them all being hipsters with a superiority complex. Try to convert me. :)

WTF?

Can we distinguish between Ruby (the language) and RoR, which is a framework (of many)

This question even irks me, this is like asking

Please compare CodeIgniter with Perl.

::emp::
 
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.

i just really like this analogy and am gonna find some way to work it into one of my conversations today