If I were (hypothetically never ) running things at Sun I'd be knocking on Howard's door until a restraining order was created or he decided to help me write a good spec. ;)
Spec? That's the thorn in Sun's side. Create useful, productive tools, not specs. Sun stops one step too short. Create an open source, high quality tool with plenty of extension points, and let the vendors differentiate on their integrations and plugins for that framework. Creating specifications so that vendors can create isolated implementations lacking in integration points (unless you are the vendor, with access to the source) is the problem. We can learn from Rails on this: focus on the tool and developer productivity (throughout the stack). Java and the open source community in general, and Tapestry in particular, has left how to be productive, how to integrate all the tools and frameworks into something useful, as an exercise to the reader. That's why there's so much desperate interest in Rails, or the comfortable suffocating hand of .Net. People want to be told what to do. I think Tapestry 5 will do that ... provide a specific way to do everything, yet allow the curtains to be pulled back to handle the exceptional cases. The IOC container is coming along great. I'm about to start on configuration data, which will lead up to contributed lifecycle models. From there, I'll be back to the true Tapestry code pretty quickly. -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
