Re: [ruby-99] Learning rails 3 - what is deal with Rails on Mobile?

From: Pradeep J.
Sent on: Friday, July 16, 2010 12:48 PM
Will,
Thanks for taking time to respond, but you did not add anything to my knowledge or about what to do in the next 1-2 years.

What you are saying is you don't have an architecture of your own, just learn whatever stuff market participants throw at you.
Your post shows your ignorance of how large scale programming systems with long life cycles are built with servers, clouds and multiple clients. This is perfectly fine for your quickies or prototyping. That is precisely my problem with RoR 2 - it seemed to be a platform for quickie one-nighters but not a sustained relationship.

Will, please don't get annoyed just because you may be a platform loyalist.
Will you are also rather rude - this is a RoR discussion group and perhaps you did not read the lines above the signature line where I asked SPECIFIC questions .. repeating for your benefit
a. What is RoR got to say "about mobile"
b. Anyone got experience with HTML5 and RoR3.
I am sure sure "objections" are met soon and RoR will become STRONGER.


--- Regards.


On 7/16/[masked]:22 PM, William Chow wrote:
Rhomobile, for all intensive purposes, sucks. I have never understood why people don't just learn Objective C and Cocoa Touch if they want to target the iPhone. 
Build your "client" application in XCode, you can build your "server" in whatever language you feel comfortable with.

When I was developing an application for the Palm Pilot, we didn't even have a relatively modern framework to deal with, we all had to program everything in C and assembly and deal with 64K memory segment barriers.

Handheld/mobile devices are limited by their nature. Don't treat them like servers and try to stick a whole mini-rails stack on it so that you can have some data input fields (which all that Rhomobile really can do).  Your application is guaranteed to suck because unlike modern day desktops, you just don't have the same amount of CPU cycles to waste. In other words, you can't afford to code bloated software on top of a bloated framework. 

I have no idea what the rest of your post is trying to get at. The stuff you listed are just a bunch of technologies, and like all technologies, you use them according to what you need to do. If you're one of those weird "paradigm architecture" folks that isn't trying to solve a real world problem, then I'd suggest you stop wasting everyone's time.

Will

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy