I just now realized what my overall, general impression of the main differences between the two methods is. I mean besides the obvious, like RoR is an entire framework while PHP is just a language, RoR is MVC and PHP is not, etc.
my general experience has been that it in Rails it is extremely easy and especially intuitive to accomplish simple tasks like creating hyperlinks to images whose names are stored in a database or listing and sorting rows of a database. for some things like this, PHP either just does it in an ugly way, is not intuitive at all, or both.
in PHP, I've found it much more simple than Rails to accomplish something more complex like file uploading. PHP, in this case, feels more "raw," and I feel like it's much easier to grasp what it's doing when you upload a file. with Rails, I couldn't even figure out how to get a file to upload.
these impressions might be because of my limited familiarity with the MVC design, my limited knowledge of Ruby, or RoR's limited documentation, but I thought they were worth putting out there to see if anyone else has experienced the same thing or thinks that they might.
and if you care, I'm going to use PHP for now, mostly because of the extensive documentation available on the Web.
my general experience has been that it in Rails it is extremely easy and especially intuitive to accomplish simple tasks like creating hyperlinks to images whose names are stored in a database or listing and sorting rows of a database. for some things like this, PHP either just does it in an ugly way, is not intuitive at all, or both.
in PHP, I've found it much more simple than Rails to accomplish something more complex like file uploading. PHP, in this case, feels more "raw," and I feel like it's much easier to grasp what it's doing when you upload a file. with Rails, I couldn't even figure out how to get a file to upload.
these impressions might be because of my limited familiarity with the MVC design, my limited knowledge of Ruby, or RoR's limited documentation, but I thought they were worth putting out there to see if anyone else has experienced the same thing or thinks that they might.
and if you care, I'm going to use PHP for now, mostly because of the extensive documentation available on the Web.
well, and a language is severely limited (or benefited) by its documentation. it's the reason that i like openbsd and dislike netbsd. the former has extensive documentation and the latter has very little.
absolutely. I have little doubt that Rails is ultimately a lot more powerful than PHP and can accomplish complex things more logically and neatly and with less code. however, the docs are the most limiting aspect of it. it sucks!
and I totally agree about Open- vs. NetBSD. NetBSD's docs are decent I'd say, but many of them aren't up to date, and no one seems to do anything about it. of course, this was my experience probably two years ago, I don't know about the current state of things.
and I totally agree about Open- vs. NetBSD. NetBSD's docs are decent I'd say, but many of them aren't up to date, and no one seems to do anything about it. of course, this was my experience probably two years ago, I don't know about the current state of things.
yeah, my experience is a year out of date.. but i doubt that netbsd has make it better that quickly.
i look forward to playing with some php frameworks and rails as well. it'll be too bad if i find a severe lack of documentation with rails.
i look forward to playing with some php frameworks and rails as well. it'll be too bad if i find a severe lack of documentation with rails.
sadly, I think that's what you're going to end up finding. even the books that I've downloaded seem pretty lacking. let me know what you think when you try it out, though.