On 11 Aug 2010, at 18:06, Fernando Perez wrote:
Remember that RoR is a framework and not a language. Compare it to
CodeIgniter, CakePHP, Symphony in the PHP space.
No RoR is a thing to build websites, as pure php, symphony, and pure
ruby do, so it is fair to compare them.
Ruby on Rails is a framework, it even says so on the rubyonrails.org
site. It was very fair of me to compare it to PHP frameworks like
Symphony, which is basically a very Rails inspired framework for PHP
developers.
Ruby is a language, as is PHP. They both can do more than serve or
generate web pages.
RoR is stuff written in Ruby that avoids writing boiler plate.
I don't know what you see as boiler plate, but considering the amount
of code in Rails, I would hardly say it's some helper functions to
build websites with database interaction quicker than from scratch.
Rails has a very well defined API, using reusable abstractions and
programming patterns to achieve a certain featureset, i.e. build web
applications, which by definition is a framework.
Beware 2 months is certainly no enough to get your app going. In real
life, a usable blog takes more than 15 minutes to get built.
It doesn't need to be. Modelwise the project seems to be quite easy,
there's only a few scenarios in there that need to be covered and by
the description alone you can clearly see the different iterations for
the project.
The most difficult part about this application is plotting out the
database structure and relationships and defining the user scenarios,
all of which are totally unrelated to Rails and should be fairly
trivial for someone in his final year of... something. Translating
them into Rails code is just browsing the API and scratching your head
every once in a while and let Google help you out.
The dangerous element will be how you will present it to the user and
you can go very fancy and get stuck into a very very timeconsuming
hell, or you can just make it simple, yet just as powerful. If you
have time left, you can then enhance the experience by refactoring
some views and sprinkling it with some functional Javascript (i.e.
something that enhances the application).
Best regards
Peter De Berdt
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
