Are you using Ruby on Rails?
If you are based in the Philippines and using Ruby on Rails, please let me know. I am compiling a list of RoR-written web applications. Email me or leave your URL and a brief description of your work.
Thanks.
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader. If you don't have a feed reader, you can always have these articles delivered to your email inbox every day. Click here to sign up.
Well I’m not technically “based” in the Philippines, although I will be returning there come March next year and am currently working on a web application for a furniture company based in Cebu.
I’m not 100% sold on ruby rails yet, and I think the initial excitement I had for the framework has been tempered somewhat with the reality that like anything, rails has a lot of problems yet to surmount before it can be a dominant platform in the market.
The best way to describe it is that its easy to scratch the surface but really difficult to dig in and deep into the framework. Most rails enthusiasts won’t know how to write rake scripts, their own helper files or accomplish a capistrano deployment but these are things that are almost certain to be required on the job or on real applications.
My worry is that a lot of developers see Rails as another silver-bullet. Sure, it takes care of a lot of things for the developer but just because you are using Rails it doesn’t mean you are going to develop applications faster. The essential difficulties of software development are still there like requirements, testing, and maintenance.
As with being sold, I am sold to Ruby on Rails. I agree there are still problems with it and much to dig in but I am betting on it.
Well said
I’m increasingly sold on Ruby on Rails, and even way back then, though not completely sold on it, I was sold enough that I’ve decided to use it for at least one major project that I have, and have created a website about my experiences with the language.
I think it is fairly important that Rails deliver in terms of development speed, but far more important is that it delivers in terms of total cost (the dreaded TCO) because this is what will sell it to companies in the end. It’s probably the reason why most of the debate surrounding Rails vs (Java/ASP.Net/PHP) is grounded mainly on the argument that the language makes it easier for developers to do things better, faster and with fewer errors. Hence the emphasis on Ruby as an elegant, expressive language and on integrated functional/unit tests in Rails the so-called holy grail of “agile” methodologies.