I think you are just trolling, but I'll reply anyways. You miss the whole point of open source and the community behind it; it's not for you to just sit and wait for somebody to do the work for you for free, but for you to develop and maintain the framework further with others. Tapestry 4.1 will not be dead till there's nobody left to pick up that work and continue. Tapestry 5 may be radically different; some of those ideas may be incorporated to future version of of Tap 4.x if you are willing to work on it. A case in point is how the ognl performance improvements came to be from the ideas in tapestry-prop and Tap5 (double hooray to Jesse for it - eagerly awaiting :). Some other ideas then might be best left for a different framework, free of the historical burden and easier to implement without having to resolve additional complexity with backwards compatibility.
Kalle On 2/4/07, nilo de roock <[EMAIL PROTECTED]> wrote:
I would like to add something. It's just not fair to call T5 'Tapestry 5', it is a -completely- new app! If Tapestry was a commercial entity clients would not accept this and the entire plan would be revoked and management sacked. The truth is that Tapestry has been pronounced dead, abandoned, end-of-life'ed. The rest is marketing. Selling a different product with an old succes name. It's called 'branding'. So what's so good about open source here?? I don't know if the license permits, but I really hope Tapestry 4.1 will be forked. The ideas in 5 are really cool and could be used as a vision for developing 4.2 but in a slower pace perhaps and without breaking code. Yes it will be more difficult, so what? What is even worse, this whole exercise could jeopardize the entire open source world. Imagine the case stories of corporations who trusted open source and are now left with dead code because no one can or wants to maintain it. I am sure some people will be very good at finding these 'cases'. It's terrible. - nilo Norbert Sándor wrote: > > I agree with you. > > I have no voice in the development of Tapestry (I know it's open source, > etc.) but if you're interested in my opinion I think it wasn't the best > idea to assign so much resource to the development of T5 before T4 is > finished. Active T5 development was started too early, now there are two > "unfinished" versions (I know that 4.1 is stable, etc. but it isn't > final yet). > Besides I'm afraid that you are right with "4.1 will be dead soon", it > seems that there will be no upgrade path from 4 to 5, these two versions > seem to be fully incompatible, they are completely different webapp > frameworks. > > Please don't misunderstand my words: I'm happy that T5 is under so heavy > development, and the developers made a wonderful job with T4.1. But I'm > afraid that T4 will be left alone soon... > > Regards: > Norbi > > nilo de roock írta: >> I am a bit confused as T5 is radically different from 4. A new app with >> the >> Tapestry 'branding'. >> Jumping on 4.1 means rewriting everything since 4.1 will be dead soon. >> T5 is not ready yet, lacks docu and components. >> Maybe pre-announcing 5 wasn't such a good thing after all? >> - nilo >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Starting-with-Tapestry-tf3170900.html#a8796909 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
