• 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: State of WebObjects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: State of WebObjects


  • Subject: Re: State of WebObjects
  • From: Paul Lynch <email@hidden>
  • Date: Wed, 28 Jun 2006 23:01:52 +0100


On 28 Jun 2006, at 22:39, Miguel Arroz wrote:

On 2006/06/28, at 22:20, Paul Lynch wrote:

You mean "fun", not "funny". That's a common misuse of English that is cropping up on lists more and more recently.

Ops... I'm not a native english speaker... what's the difference?

"Fun" is enjoyable; "funny" is humourous.

I'm going to disagree with the initial point of this. WO and Rails take exactly as long as each other to get started with your first working app. The "learning curve" is more or less the same for both technologies. Rails is most emphatically NOT simple; it is a complex framework, exactly as it should be. The tradeoffs between Rails and WO are there, and general opinion here gives WO the edge still; search this list for a couple of good comparisions between the two.

I'm not so sure. I see many web-designers creating simple rails apps, or at least editing the interface code. I don't see them doing this with WO. Of course, rails community tries to spread the ideia that "Rails is so easy, even you can do it", so this will at some point convince people that they can do apps without learning (despite the fact that they ARE learning). But I still think you need to understand a lot more concepts if you want to work with WO than with rails.

I still don't see this. A Rails scaffolding app is analogous to a WO Wizard or D2W app; they both have the same advantages and disadvantages, and take roughly the same amount of time to set up. If you don't see people using WO to do this, it doesn't mean that it can't be done - it just means that Rails is the latest flavour of the month, evangelical product.


As for the concepts, there are just as many. You still need to learn the frameworks, and Rails has a lot of things that aren't intuitively obvious (just the same as WO, only different); the naming conventions, for one thing. The only real difference I see is that WO is fanatical about MVC (in comparison to Rails), and Rails likes to blur the edges. This could be a really important difference, and quite possibly the only significant one.

Paul
_______________________________________________
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: State of WebObjects
      • From: Mike Schrag <email@hidden>
References: 
 >State of WebObjects (From: Scott Henderson <email@hidden>)
 >Re: State of WebObjects (From: David LeBer <email@hidden>)
 >Re: State of WebObjects (From: Miguel Arroz <email@hidden>)
 >Re: State of WebObjects (From: Paul Lynch <email@hidden>)
 >Re: State of WebObjects (From: Miguel Arroz <email@hidden>)

  • Prev by Date: Re: State of WebObjects
  • Next by Date: Re: State of WebObjects
  • Previous by thread: Re: State of WebObjects
  • Next by thread: Re: State of WebObjects
  • Index(es):
    • Date
    • Thread