ICEknight, on 04 April 2012 - 12:54 PM, said:
Rolken, on 03 April 2012 - 01:39 PM, said:
For similar reasons, PHP itself is neither the present nor future of web development, it's the past. Rails is the present, and Node.js is the future.
I'd love to read why you have that oppinion...
Rails lets you do more in less time with less hassle.
Node.js is even more seamless (a web server stub is six lines of code), but it's too young to have as much framework support as Rails, which is why it's the future and not the present. I'm using it for a personal project, but I can't objectively recommend it as The Way.
Honestly, the biggest problem with PHP is that it encourages subpar coders to produce subpar code, in the same way that IE6 taught all the HTML-slingers that they could write bullshit HTML and reload until it looked right, only now the playing field is SQL injections and URL hacking. And since you're talking specifically about future projects of unbounded complexity, I would strongly recommend spending a day apprising yourself of all the options, if nothing else just so you know what's out there.
Rather than pontificate all day, if you're interested, here's an example guide
comparing CodeIgniter and Rails directly. It's a couple years old, so you might want to skim it rather than take it as line-for-line gospel. To see the latest state of Rails, try the official getting started guide
edit: just found a fantastic summary of the state of node.js
, its advantages, and what's holding it back (so far), with bonus observations on the ascent of Rails.
This post has been edited by Rolken: 04 April 2012 - 02:19 PM