addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

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

From: William C.
Sent on: Friday, July 16, 2010 6:06 PM
Jain:

On the contrary, I just saved you a lot of time on going down the wrong path with Rhomobile or whatever framework you are contemplating on using for mobile. If you insist on not listening to good advice <shrug> that's of course your prerogative. I've looked at Rhomobile, I met the guys who do Rhomobile. The framework just plain sucks. It takes too many steps to get from Ruby to a Cocoa Touch binary. It's a nice idea, and if the Iphone itself was not such a constrained device, I'm sure Ruby would be a decent RAD tool for it. But you shouldn't use Ruby to run small devices, it's just not an appropriate place for it.

As for the architecture dig, architectures are obviously system dependent. Being an "architecture" zealot is akin to attempting to solve every home improvement problem with a hammer. Speaking about architectures without context is, as I stated before, pretty much a waste of time. It's an interesting mental exercise, but speaking from years of experience, simple, clear-cut systems are the best. Piling on architecture after architecture is what got us bloatware like J2EE (or whatever they decide to call it these days). 

Obviously you have never deployed even one production RoR site, because there's plenty of places that utilize RoR in development systems (and yes, I've worked at multiple real world places that utilize RoR, and I continue to work as a RoR developer). 
If you want to figure out if RoR is for you, then ask some real questions, i.e. "I have application XYZ in mind, is RoR a good solution?"

Sorry that you feel insulted by my rudeness. Unlike other posts in the past, it WAS meant to be somewhat rude, because I personally am rather tired of people posting essentially nonsense posts about "architecture" without context.
Also, you're just essentially attempting to flame-bait when you attempt to attack RoR in not-so-subtle ways when posting to an RoR meet up group. We've had enough flame baiters in the past, so the whole point is:

A) Are you attempting to ask some real questions, or do you want to talk about pie-in-the-sky crud?
B) Why are you so hung up about HTML5, the cloud, mobile, architecture, why the sky is blue, the world is round, etc. etc.?

In short, what's your point?

As for the personal attacks, as always, water off a ducks back. Ad hominem attacks are pointless to rebut. I can call you an idiot too and it wouldn't make much difference. 


Will


On Jul 16, 2010, at 12:49 PM, Phillip Jain <[address removed]> wrote:

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





--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Phillip Jain ([address removed]) from Silicon Valley Ruby Meetup.
To learn more about Phillip Jain, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here

Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]

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