This is an interesting "guess". Is that 70% more than a guess or is there some basis to think that?
On 12/1/05, Ted Husted <[EMAIL PROTECTED]> wrote: > On 12/1/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > But the fact that Struts has always stressed backwards > > compatibility of the key APIs as a fundamental principle is one of they key > > reasons that it has been successful. > > Hmmm, perhaps, but not for the obvious reason. I'd guess that 70% of > the 70% marketshare that Struts is suppose to have is still using 1.1. > In practice, what we've done with 1.2 or 1.3 only matters to a small > fraction of Struts users. Of course, backward compatability is very > important to the *committers*, since we are more likely to upgrade > existing applications, or start new projects with the latest versions, > and, being only human, we want that process to go smoothly for > ourselves. > > While backward compatibility has played a role, I think it has been > more of a "feel good" factor than something that made a practical > difference to the user base. I think we can make Ti very compatible > with 1.3.0, but, more importantly, we need to show people how > compatible existing skill sets and design paradigms are with > TI/WebWork. It's not a bad thing to do things a little bit differently > if different is a lot better. Witness JSTL. > > -Ted. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
