FMSA vs. WebObjects vs. Java Framework vs. Scratch

[Gordie]

Hi,

I'm going to pose a question that can't be completely answered because I haven't developed the requirements fully enough, but I'm just looking for folks' overall thoughts.

I am planning on building a Web site to support a consulting activity, and I am trying to figure out the pluses and minuses of various technologies as I figure out my solution.

Top level requirements/wants:

- Customized user interface (throws out IWP) to include search capabilities using standard Boolean queries

- Good security, not only access control, but may also want each clients data encrypted separately

- Reasonably powerful development tools (consulting is the objective, not Web site development), but also a reasonable learning curve

- May want to provide clients the possiblity of hosting their own solution for those companies that don't want to outsource apps with sensitive data

My experience:

- Standalone/IWP FM databases - not an expert, but good enough

- Okay at Java programming but am not experienced in the bazillion frameworks that conceivably can be used for everything from Web site development to mowing the lawn (okay, a little exageration...)

- Some experience a couple of years ago in XML/XSLT - enough to know that there is a little bit of a steep learning curve, but it isn't insurmountable

My first inclination was to go with WebObjects because I thought it would handle a lot of the UI for me, thus speeding up things. However, my investigation (no experience) is that if you want a decent UI, you're gonna have to write it yourself (not sure how much Interface Builder helps out, though). Plus, while the WO equivalent to IWP seems to be pretty straightforward, customization requires learning a fair amount about WO.

I would love to do this with FMSA, but it is somewhat more expensive (WO went from $50,000 to $699 while FMS(A) went from $500 to $2500...), and I've read on these forums about little problems, including security, and perhaps some customization issues that make me leery. However, an FM solution would give me a great way to scale solutions hosted by the customer (standalone, one-person FMDev solution all the way up to the full enchilada hosted on an intranet).

As much as I like Java, I am concerned about pursuing the various frameworks (e.g., Struts) or even PHP for fear that I'll spend weeks just figuring out "Hello World."

I also could home grow a solution, and that would let me use an object database rather than relational one, but what sounds nifty now might turn out to be one where I have to recreate everything starting from F=ma and E=mc2 (and maintain it), thus negating the short learning curve for this choice.

Okay, enough rambling. Does anyone have a general opinion on this? I realize there's not enough information here to make a complete objective analysis, I would just like to hear success/horror stories from others who have grappled with this choice.

Thanks,

Gordie