• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WO vs. Ruby on Rails
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO vs. Ruby on Rails


  • Subject: Re: WO vs. Ruby on Rails
  • From: David LeBer <email@hidden>
  • Date: Fri, 14 Mar 2008 10:10:57 -0400


On 14-Mar-08, at 9:51 AM, Andrew R. Kinnie wrote:

Greetings,

I am know this has been covered repeatedly, but I just went to a mac developers group meeting last night (in Northern Virginia), and there was a demonstration of ruby on rails development on a mac, and three of the people were gushing about how great it is, and no one (other than me. . . to a limited extent) even mentioned WO. Does anyone have any new insight about why people should consider WO instead of Ruby on Rails?

It depends on what you are trying to do.

ROR makes perfect sense for some projects. WO makes perfect sense for others. And sometimes it's a coin toss as to which one to use.

Personally I am most productive with WO, and it leaves me with the fewest concerns about scalability and whether I'm going to hit limitations when managing my object graph.


It seems everyone everywhere (outside of this list) thinks that WO has been left to "whither on the vine" or "had some really advanced technology" before being left to whither on the vine, etc.

Yeah, well, that's just life in the WO world. Those who know do. Those that doubt do. Those that don't know don't.


Anyone who has watched what has happened in the community over the past 3-4 years would would think that was a weird example of 'withering on the vine'

Ideally, I'd love to be able to do a demo of WO and WOLips/Wonder, etc. at a future meeting, but I am not up to the necessary level of expertise to field the questions from these guys. I have worked with webobjects on and off over the years, but I'd like a better argument than I can make with my unfortunately limited recent involvement.

You can always watch the vidcasts on the WOCommunity site and try and recreate them live. When it comes to questions: "that is an interesting question, I'll have to get back to you on that" is a line that usually works well for me. Bringing the list your questions will often get them answered quickly. But, sometimes there are arguments you just can't win. If you encounter a ROR (or any other tech) zealot, no amount of logic is going to stop them from giving you the "we are the future, all that old technology suxs" line.


Any suggestions, insight would be helpful.

The fact that everyone on the planet is not using your technology of choice doesn't mean you're wrong. It might just mean you have a competitive advantage.


;david

--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site:   http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: WO vs. Ruby on Rails
      • From: Mike Schrag <email@hidden>
References: 
 >WO vs. Ruby on Rails (From: "Andrew R. Kinnie" <email@hidden>)

  • Prev by Date: Re: WO vs. Ruby on Rails
  • Next by Date: Re: WO vs. Ruby on Rails
  • Previous by thread: Re: WO vs. Ruby on Rails
  • Next by thread: Re: WO vs. Ruby on Rails
  • Index(es):
    • Date
    • Thread