[This is the second part of this post]
Getting back from
Symfony to
Ruby-on-Rails was a big relief! There is no comparison between Ruby and PHP. Anything said on the matter is wasted. Anyway since I had my troubles solved by the hosting company, now I had my first RoR application running on the server. Then I tried to elaborate it, and like immediately found a problem. The problem was internationalization
(i18n)! It seems that Rails was not developed with i18n in mind from the beginning and its current version does not support it! You have to hack your way to it. In my mind i18n is a big and necessary feature for web. After all it is the
World Wide Web! It turns out that Rails has a major problem with i18n what goes down to the language itself. Ruby does not support
unicode for string representation. (
actually it does but with the use of a module, not natively). However in version 2.2 of Rails, which is currently the
edge version, they included basic i18n support. This meant that I had to use the “unstable” branch of Rails – which I did! Checked out the way i18n support was implemented and found it very basic. This is by design. The developers of Rails want
Read the rest of this entry »