On Jan 9, 2011, at 3:34 PM, gezope wrote:
I think Rails is for web applications. First of all you have to decide if your application will contact to the net? It seems not this is the main functionality of your application, and noone will check his cancer on Facebook.
I've built two intranet applications for a medical device manufacturer so far, more to come. I think that depending on the application, you can get a lot of mileage out of a web app. For one thing, the cost of supporting the desktop drops by a huge factor. For another, rolling out updates is completely trivial, with no need to traipse around to each desktop (or location, in a more widely-distributed organization) to make sure that everybody has the same version. I'm not saying that every problem is a nail, but you can get a long way through a lot of different types of problems without crossing the boundary into native application-land.
Walter -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
