Something in your observations has struck a chord..
5. Perceived to be a "consultant's framework" in that it changes enough - and (back to the tooling) without tool support - that only consultants can keep up with how to migrate from version to version.
This is absolutely true and it goes way beyond Tapestry's wild evolution path. Tapestry is now a framework built by constants and by not choosing reasonable conventions and sticking to them Tapestry panders to consultants. By that I mean consultants in the conventional sense but also consutants in the sense of the guru guy everyone in the company "consults" with about Tapestry as the guru knows more than anyone else. Here are observations I made working as that resident Tap guru in a high pressure development group using T3: There are too many ways to do things and people for the most part don't care and continually ask why there these options exist. Or don't ask 'cuz they stopped caring. I was becoming like a folk story teller, explaining the options and why they came to be. Sometimes I don't know why. So I stopped doing that. Not being a high paid consultant here there is no advantage to pumping up my image by expounding on my vast knowledge of Tapestry. Everybody knows that I know more about T than they do. They want that nugget of info needed to solve the problem at hand and image pumping is seen as waste of time. As for T4 and migrating: Not going to happen here. A huge investment has gone into the current T3 apps. No funding is going to come for porting apps that work perfectly well for no percieved, and immediate, advantage. Plus there are aspects to T4 that I think also cause friction... I know that having me as the only guru was considered a risk by the powers that be. What if I bailed? The only other hire they had that knew T before arriving punched out after 5 months. Turn over here is not high but I expect it to rise as the industry picks up in town. After a year they have 9-10 people proficient in Tapestry 3 and don't want to repeat the growing pains we encountered previously when only 2 people in the room were comfortable with T. And that would happen if there was a T4 port. Hivemind is "yet another technology to learn" and when I described that most could get by without using it the response was "Yes, but that means only a few, probably just you, will know it and then we are vulnerable if you leave" We now have 5 large T3 products either in production or development. Porting all at once is out of the question and that means some working in T3 and some in T4 - not going to happen. My 2 cents. Geoff -- The Spindle guy. http://spindle.sf.net Blog: http://jroller.com/page/glongman Other interests: http://www.squidoo.com/spaceelevator/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
