On Feb 9, 10:45 am, “Phlip” [email protected] wrote:
talking it - yet I had the impression it grew out of a Perl customized
From my memory, PHP was originally the “Personal Home Page” engine for
the original developer, basically to show off his skills to potential
employers. It grew organically and started including all sorts of
third party libraries, and was the defacto standard competing with
Cold Fusion for a long time (still probably is).
Given its history, it is not surprising that many of the best practice
techniques in (web) development are not present or baked into the
application (I don;t really like calling it a framework). Rails
however was designed from the start around MVC, OOP, classes,
inheritance, testing, etc. It leverages the friendly “optimised for
happiness” environment that Ruby provides. The more I learn Rails,
the more I realise I am learning Ruby and it’s tricks.
Coming from a PHP background I appreciate Ruby and Rails a whole lot
more. It does provide a lot of magic if you follow the conventions
(learning exactly what they are is the hard bit at the moment).
You may be better off in the long run if you do some PHP for a while,
but keep tinkering with Rails in the background. Show you can do it
in PHP, but then how it can be done in Rails. There is nothing more
demoralizing than seeing someone implement what you have been doing in
PHP for the past week do it in 1 day in Rails in fewer, more readable
LOC and better flexibility.