It seems to me that Tapestry is swimming quite well just now. It's not just Marc's inflammatory remarks - this forum has had a noticeable increase in traffic recently. Also seems to me that there has been something of a sudden uptake by WO developers. If you want to get Tapestry out into a lot of places where the barrier to its 'complexity' is low, then targetting WO developers is likely going to be the biggest bang-for-buck option. More developers -> more contributors -> faster swimming. Any ideas from WO folk here as to how Tapestry uptake might be encouraged for WO developers (rather than JSP developers)?
R ----- Original Message ----- From: "Howard M. Lewis Ship" <[EMAIL PROTECTED]> To: "Tapestry Developer" <[EMAIL PROTECTED]> Sent: Friday, October 11, 2002 1:24 AM Subject: [Tapestry-developer] Consistency vs. Ease of Adoption ... Philosophy: There's now two ways of doing the same thing. Marc embraces this, but there's general resistance to it elsewhere. There may be ugly interactions between the two models. Many people *will* misuse it because it is simple startup (you must always throw away the first prototype, but most don't). I've seen some responses that say Tapestry simply isn't for the masses, but I just don't buy it. At the core, Tapestry is simpler than other frameworks and more powerful, it should be much more widely adopted. I buy into the "shark" theory ... keep swimming or die, Tapestry must extend its range or it will never escape niche status and will eventually die off. Tapestry RAD could be the thing that gets Tapestry in front of a lot more eyeballs. ---- Howard Lewis Ship [EMAIL PROTECTED] http://tapestry.sf.net ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
