<jokingly> Wow Ted, that was just about the most cliche-ridden post I've seen in a while :) If that's what you were going for, mission accomplished! LOL </jokingly>
Of course, every single cliche you used is completely true and applicable here, so no one minds I'm sure :) -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] On Fri, February 10, 2006 4:17 pm, Ted Husted said: > On 2/10/06, Vu, Thai <[EMAIL PROTECTED]> wrote: >>. Now what should I use if I >> have to write a new web application? And correct me if I'm wrong >> anywhere please. > > It's a little bit like asking a building contractor: "What materials > should I use to build a new structure?" > > Just to pose a few rhetoric questions: Are you a sole developer > building a five page application next week, or leading a team of ten > developers building a five hundred application over the next year or > two? Is the primary purpose of the application database access or > something else? How important is look and feel? Are the java > developers doing the markup, or is there a second team of HTML > designers? Are you expected to use prepared statements, code your own > SQL, or have it generated? Will the site be static or have a number of > dynamic elements? How soon before the site needs to be updated (if > ever)? Are the requirement stable, or are the business people still > figuring out what they want? Will the site need to maintained and > extended as business needs change, or would you start from scratch > with a new site? > > Now some vendors want you to believe that no matter how you answer any > of these questions, and a hundred more, there is only one true answer: > Whatever product they want to sell you! > > One size fits all is a myth. We don't have a unified theory of > relativity, and we don't have a unified framework for web development > at all scales. Some things work better for small applications > (Quantum). Somethings work better for larger application (Relativity). > There is a tipping point when you need to shift gears from > quick-and-easy to extensible-and-robust. > > It's one thing to build a bike-shed; it's another to build a skyscraper. > > A professional chooses the right tool for the job. To a PHB, every > application is a nail. > > My best advice is to pick the smallest possible part of your > application and try that part with a couple of likely technologies. > Then, choose the one that best suits the application, your team, and > you. > > If it is not worth the trouble of doing even a small part more than > once, then the job is probably a small enough job that you can snag > Java Studio Enterprise and do it with JSF out of the box. > > * > http://developers.sun.com/prodtech/javatools/jsenterprise/reference/techart/whatis.html > > HTH, Ted. > > http://husted.com/blog/ted/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
